Repository navigation
chore(release): version vecstore-sdk as 0.3.0 instead of 0.2.0 - #92
Conversation
The version pull request (#90) computed 0.2.0 for the first minor release on 0.1.x. That version was published and unpublished on 2026-09-10, and npm never accepts a version twice, so the Release job failed at publish. 0.3.0 has never been published. The changelog entries stay the same.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
commit: |
Background
The goal is to ship
scanandunwrapto npm. The Release run after #90 failed at publish (run 43626419803):Cannot publish over previously published version "0.2.0". The first minor changeset on 0.1.x made changesets compute 0.2.0. That version was published and unpublished on 2026-09-10. npm never accepts a version twice, so 0.2.0 can never ship.Summary
packages/vecstore-sdk/package.jsonand the topCHANGELOG.mdheading to 0.3.0. The changelog entries stay the same.release.ymlruns on a push only when the push changes.changeset/, and this change does not. To publish, run theReleaseworkflow from the Actions tab with Publish a snapshot release unchecked. With no changesets left, the changesets action runsbun run release, which builds, tests, checks, and publishes 0.3.0.Verification
bun run check:release, the Release job's pre-publish gate, exits 0: 735 tests pass, 0 fail, and the package checks pass.npm pack --dry-runinpackages/vecstore-sdkreportsvecstore-sdk-0.3.0.tgz.npm view vecstore-sdk@0.3.0returnsE404 No match found for version 0.3.0. Thetimemap of the package lists 0.2.0 but not 0.3.0.Checklist
vecstore-sdk. Not applicable: a changeset would bump the version again. This pull request has theskip-changesetlabel.Summary by CodeRabbit