chore(release): bump package.json to v0.21.42 - #1745
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)
Comment |
There was a problem hiding this comment.
Pull request overview
This PR keeps the repository’s version metadata aligned with the just-published npm release (@sistent/sistent@0.21.42), preventing master from drifting behind published versions.
Changes:
- Bump
package.jsonversion from0.21.41to0.21.42. - Update corresponding version fields in
package-lock.jsonto0.21.42.
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.42 to match the published npm release. |
| package-lock.json | Syncs lockfile version fields to 0.21.42 for consistency with package.json. |
Bumps
package.jsonandpackage-lock.jsontov0.21.42to 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