debumped to 2.0.2

[gin0115]

Changes proposed in this Pull Request

Revers bumping to 2.0.3 as 2.0.2 was never released (juts tested locally/staging)

Testing instructions

Mentions #

Summary by CodeRabbit

• Chores
  • Downgraded the plugin version from 2.0.3 to 2.0.2 in all relevant metadata and version references.

[coderabbitai]

Walkthrough

The changes in this update involve downgrading the version number from 2.0.3 to 2.0.2 across two files: package.json and plugin.php. In package.json, only the version field was modified. In plugin.php, the version number was updated in the file header, the plugin header comment block, and the SE_VERSION constant. No other content, structure, or functional code was altered. No new public or exported entities were introduced or removed.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 5610c7d and 39edcbe.

📒 Files selected for processing (2)

• package.json (1 hunks)
• plugin.php (3 hunks)

🔇 Additional comments (2)

package.json (1)

3-3: No residual project version references outside lockfiles

I ran rg -n '"?2\.0\.3"?' and confirmed that the only matches are in composer.lock and package-lock.json (dependency pins). There are no 2.0.3 occurrences in README.md, CHANGELOG.md, deployment scripts, or inline docs. All other artifacts correctly reference 2.0.2.

plugin.php (1)

6-7: Version constants & headers kept in sync – LGTM

The rollback is consistently applied in the file-header @version, plugin header Version:, and SE_VERSION constant. No functional code paths rely on the former value, so this is safe.

Also applies to: 16-16, 34-34

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.