Release/2.0.6

[gin0115]

Changes proposed in this Pull Request

• Fixes ical issue

Testing instructions

Mentions #41

Summary by CodeRabbit

• Chores
  • Bumped package version to 2.0.6 for a patch release.
  • Updated development coding standards dependency to target the 3.1.x series.
  • Minor formatting cleanups (e.g., trailing newline consistency).
• Documentation
  • Updated plugin header metadata to reflect version 2.0.6.

No functional or behavioral changes; this release focuses on metadata alignment and developer tooling updates to maintain consistency and improve code quality checks.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

• composer.json: Updates require-dev constraint for wp-coding-standards/wpcs from "^3.0" to "3.1.*" and adds a trailing newline.
• package.json: Bumps version from 2.0.5 to 2.0.6 and adds a trailing newline.
• plugin.php: Updates plugin header metadata version from 2.0.5 to 2.0.6; no runtime code changes. The SE_VERSION constant remains '2.0.5'.

Possibly related PRs

• Release/2.0.4 #37: Also updates release/version metadata in package.json and plugin.php.
• bumped #34: Similar version bump work; additionally updates the SE_VERSION constant, unlike this PR.
• bumped to 2.0.5 #39: Performs package.json and plugin header version updates akin to this PR.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ba581b and e3f8310.

⛔ Files ignored due to path filters (1)

• composer.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• composer.json (2 hunks)
• package.json (2 hunks)
• plugin.php (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}