Bumped

[gin0115]

Changes proposed in this Pull Request

This pull request includes a version bump for the wpcomsp-simple-events plugin from 2.0.2 to 2.0.3. The changes ensure consistency across the plugin's metadata and version definitions.

Version update:

• package.json: Updated the version field to 2.0.3.
• plugin.php: Updated the version in the plugin header comments (@version, Version) to 2.0.3. [1] [2]
• plugin.php: Updated the SE_VERSION constant to 2.0.3.

Testing instructions

Mentions #

Summary by CodeRabbit

• Chores
  • Updated version number to 2.0.3 throughout the application.

[coderabbitai]

Walkthrough

The changes involve updating the version number from 2.0.2 to 2.0.3 in both the package.json file and the plugin.php file. In package.json, only the version field was modified. In plugin.php, the version was updated in the file header docblock, the plugin header comment block, and the SE_VERSION constant definition. No other content, structure, or exported/public entities were altered aside from the version constant.

Note

⚡️ Unit Test Generation is now available in beta!

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

✨ 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

package.json (1)

3-3: Version bump is correct & consistent across metadata

The version field is now 2.0.3, matching the plugin bootstrap. No issues spotted.

Consider updating any CHANGELOG or release-notes file (if maintained) in the same commit, so consumers immediately see what changed.

plugin.php (1)

6-7: Header & constant updated to 2.0.3 — looks good

All three occurrences (docblock, plugin header, SE_VERSION constant) are in sync. No functional impact, so the bump is safe.

If the project keeps a readme.txt/README.md “Stable tag” or similar field for WP.org distribution, make sure it’s also bumped to 2.0.3 to avoid mismatches.

Also applies to: 16-17, 34-34

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ffb0654 and 7659097.

📒 Files selected for processing (2)

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