chore(release): bump package.json to v0.21.25#1658
Conversation
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Code Review
This pull request updates the version of the @sistent/sistent package from 0.21.24 to 0.21.25 in both package.json and package-lock.json. I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
Pull request overview
Aligns the repository’s tracked package version with the already-published npm release (v0.21.25) to prevent master from drifting behind the published artifact.
Changes:
- Bump
package.jsonversion from0.21.24to0.21.25. - Update corresponding
package-lock.jsonversion fields to0.21.25.
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.25. |
| package-lock.json | Syncs lockfile version metadata to 0.21.25 (top-level and root package entry). |
Bumps
package.jsonandpackage-lock.jsontov0.21.25to 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.