chore(release): bump package.json to v0.21.41 - #1740
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 version update
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested labels: Suggested reviewers: ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install timed out. The project may have too many dependencies for the sandbox. Comment |
There was a problem hiding this comment.
Pull request overview
Synchronizes the repository’s recorded package version with the already-published npm release (v0.21.41), preventing master from drifting behind npm and reducing downstream confusion for contributors.
Changes:
- Bump
package.jsonversion from0.21.40to0.21.41. - Update
package-lock.jsonto reflect the same0.21.41version at both the root and package entry.
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.21.41 to match the published npm release. |
| package-lock.json | Aligns lockfile version fields with 0.21.41 to keep install metadata consistent. |
Bumps
package.jsonandpackage-lock.jsontov0.21.41to 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