Skip to content

Bumped all version definitions to 2.1.0 and re compiled package-lock#70

Merged
gin0115 merged 1 commit into
trunkfrom
release/2.1.0
Mar 27, 2026
Merged

Bumped all version definitions to 2.1.0 and re compiled package-lock#70
gin0115 merged 1 commit into
trunkfrom
release/2.1.0

Conversation

@gin0115

@gin0115 gin0115 commented Mar 19, 2026

Copy link
Copy Markdown
Collaborator

Changes proposed in this Pull Request

  • Bumps to 2.1.0 to account for the auto update functionality being in place

Testing instructions

Mentions #

Summary by CodeRabbit

  • Chores
    • Updated plugin version to 2.1.0

@coderabbitai

coderabbitai Bot commented Mar 19, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5cf6de8b-57ef-4f9e-a225-6fdfb4cffb33

📥 Commits

Reviewing files that changed from the base of the PR and between ed3ee0f and a820c73.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • package.json
  • plugin.php

Walkthrough

The plugin version was updated from 2.0.13 to 2.1.0 across multiple files. In package.json, the version field was incremented and the file was normalized to include a newline at the end. In plugin.php, the version metadata was updated in the header docblock (both @version and Version fields) and in the SE_VERSION constant definition. No functional changes to logic, control flow, or behavior were introduced.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main changes: version bumps to 2.1.0 and package-lock recompilation, matching the file-level changes in package.json and plugin.php.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
📝 Coding Plan
  • Generate coding plan for human review comments

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

@gin0115 gin0115 merged commit f337b5a into trunk Mar 27, 2026
7 checks passed
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