chore(release): bump package.json to v0.22.3 - #1797
Conversation
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe package version in ChangesPackage release
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
This PR syncs the repository’s package.json and package-lock.json version fields to 0.22.3, aligning master with the version already published to npm and preventing version drift in contributor checkouts.
Changes:
- Bump
package.jsonversion from0.22.2→0.22.3. - Bump root and workspace package version entries in
package-lock.jsonfrom0.22.2→0.22.3.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Updates the package version to 0.22.3 to match the published npm release. |
| package-lock.json | Updates lockfile version metadata to 0.22.3 to stay consistent with package.json. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Bumps
package.jsonandpackage-lock.jsontov0.22.3to match the version just published to npm.This PR is auto-generated by the
Publish Node.js Packageworkflow after a successfulnpm publish --provenanceso that the target branch tracks the published npm version rather than drifting behind it indefinitely. Historically this drift has confused contributors branching offmaster(e.g.,masterwas at0.16.5while npm had publishedv0.18.8).The commit message includes
[skip ci]so merging this PR does not re-trigger workflows against the bump commit — the content was already CI-gated by the PR that merged into the tag.Summary by CodeRabbit