chore(release): bump package.json to v0.21.19#1610
Conversation
Signed-off-by: Lee Calcote <leecalcote@gmail.com>
There was a problem hiding this comment.
Code Review
This pull request downgrades the version of the @sistent/sistent package from 0.22.0 to 0.21.19 in both package.json and package-lock.json. There are no review comments to evaluate, and 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 declared package version on master with the version actually published to npm (0.21.19) by reverting the previously-ahead 0.22.0 version metadata. This keeps the source-of-truth version in sync for downstream consumers and future release automation.
Changes:
- Update
package.jsonpackage version from0.22.0to0.21.19. - Update
package-lock.jsontop-level and root package entry version from0.22.0to0.21.19.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Sets the package version to 0.21.19 to match the published npm release. |
| package-lock.json | Keeps the lockfile’s recorded package version consistent with package.json (0.21.19). |
Bumps
package.jsonandpackage-lock.jsontov0.21.19to match the version just published to npm.This is the version-bump-back that the
Publish Node.js Packageworkflow normally opens automatically after a successfulnpm publish. For thev0.21.19release the automated step failed (git exit 128) because the workflow passedbase: refs/heads/master(a full ref) instead of the shortmaster, sopeter-evans/create-pull-requestrefused to fetch into the checked-out branch. Opening it manually here.Brings
master(which had drifted ahead to0.22.0without a matching npm publish) back in line with the actually-published0.21.19.The commit message carries
[skip ci]so merging does not re-trigger workflows against the bump commit.