Skip to content

bumped to 2.0.5#39

Merged
gin0115 merged 1 commit intotrunkfrom
release/2.0.5
Aug 15, 2025
Merged

bumped to 2.0.5#39
gin0115 merged 1 commit intotrunkfrom
release/2.0.5

Conversation

@gin0115
Copy link
Collaborator

@gin0115 gin0115 commented Aug 15, 2025

Changes proposed in this Pull Request

  • Bump to 2.0.5

Testing instructions

Mentions #

Summary by CodeRabbit

  • Chores
    • Bumped product version to 2.0.5 for release tracking and consistency across interfaces.
    • Updated displayed version information where applicable.
    • No user-facing features or fixes included; behavior and functionality remain unchanged.
    • Compatibility is unaffected; no configuration updates or actions required.
    • All existing workflows continue to operate as before.

@coderabbitai
Copy link

coderabbitai bot commented Aug 15, 2025

Walkthrough

This PR increments the project version from 2.0.4 to 2.0.5. In package.json, only the version field changes. In plugin.php, the header Version and @Version fields are updated to 2.0.5, and the SE_VERSION constant is set to '2.0.5'. No code logic, APIs, or dependencies are modified.

Possibly related PRs

  • Bumped #28: Bumps package.json version and updates plugin.php header and SE_VERSION constant.
  • debumped to 2.0.2 #31: Updates the same version identifiers in package.json and plugin.php (SE_VERSION).
  • bumped #34: Performs identical version increments in package.json and plugin.php.

Suggested reviewers

  • joao-krauchenco-mottu

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between ec1beae and a3a7922.

📒 Files selected for processing (2)
  • package.json (2 hunks)
  • plugin.php (3 hunks)
🔇 Additional comments (3)
package.json (1)

3-3: Version field bumped to 2.0.5 — LGTM

Matches plugin.php updates; no functional changes.

plugin.php (2)

6-6: Docblock @Version updated to 2.0.5 — LGTM

Consistent with the package manifest.


16-16: Plugin header Version updated to 2.0.5 — LGTM

Header metadata reflects the release version correctly.

define( 'SE_METADATA', get_plugin_data( __FILE__, false, false ) );

define( 'SE_VERSION', '2.0.4' );
define( 'SE_VERSION', '2.0.5' );
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Avoid version drift: define SE_VERSION from header metadata

Optional improvement to keep a single source of truth and avoid future mismatches. Define SE_VERSION from SE_METADATA['Version'] so you don’t need to manually update it each release.

Apply this diff:

-define( 'SE_VERSION', '2.0.5' );
+define( 'SE_VERSION', SE_METADATA['Version'] );

Run this script to verify all version references are aligned and no stale 2.0.4 remains:


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Extract versions
pkg=$(jq -r '.version' package.json)
php_header=$(sed -nE 's/^\s*\*\s*Version:\s*([0-9.]+)\s*$/\1/p' plugin.php | head -n1)
php_constant=$(rg -nP "define\(\s*'SE_VERSION'\s*,\s*'([^']+)'\s*\);" plugin.php -r '$1' -N -o || true)

echo "package.json version:        $pkg"
echo "plugin.php header Version:   $php_header"
echo "plugin.php SE_VERSION const: ${php_constant:-<derived or not found>}"

# Compare values
[[ "$pkg" == "$php_header" ]] || { echo "Mismatch: package.json vs plugin header."; exit 1; }
if [[ -n "${php_constant}" ]]; then
  [[ "$pkg" == "$php_constant" ]] || { echo "Mismatch: package.json vs SE_VERSION constant."; exit 1; }
fi

echo "Scanning for stale old version references (2.0.4)..."
if rg -nP '\b2\.0\.4\b' -g '!vendor/**' -g '!build/**' -g '!dist/**' ; then
  echo "Found stale 2.0.4 references above."; exit 1
else
  echo "No stale 2.0.4 references found."
fi

Length of output: 3934


To ensure the suggested change will work, let’s first confirm that SE_METADATA is actually defined in the plugin and contains a Version key.


🏁 Script executed:

#!/bin/bash
# Search for where SE_METADATA is defined or populated
rg -n "SE_METADATA" -g "*.php" -C3

Length of output: 412


Use header metadata as the source of truth for SE_VERSION

Derive the plugin constant from the parsed header to avoid manual updates.

  • plugin.php (around line 34)
-define( 'SE_VERSION', '2.0.5' );
+define( 'SE_VERSION', SE_METADATA['Version'] );

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In plugin.php around line 34, SE_VERSION is hardcoded; instead parse the plugin
header and derive the constant from the parsed "Version" header. Use WordPress's
get_file_data(__FILE__, ['Version' => 'Version']) (or a small header-parser
fallback if WP functions are not available), grab the Version value,
sanitize/trim it, default to a safe fallback if missing, and then
define('SE_VERSION', $version) only if not already defined.

@gin0115 gin0115 merged commit b5b48b9 into trunk Aug 15, 2025
7 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Sep 9, 2025
This was referenced Sep 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant