Skip to content

chore(release): version vecstore-sdk as 0.3.0 instead of 0.2.0 - #92

Merged
PunGrumpy merged 1 commit into
mainfrom
chore/release-0-3-0
Nov 14, 2026
Merged

PunGrumpy merged 1 commit into
mainfrom
chore/release-0-3-0

Conversation

@PunGrumpy

@PunGrumpy PunGrumpy commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

Background

The goal is to ship scan and unwrap to 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

  • Set packages/vecstore-sdk/package.json and the top CHANGELOG.md heading to 0.3.0. The changelog entries stay the same.
  • Merging this does not publish. release.yml runs on a push only when the push changes .changeset/, and this change does not. To publish, run the Release workflow from the Actions tab with Publish a snapshot release unchecked. With no changesets left, the changesets action runs bun run release, which builds, tests, checks, and publishes 0.3.0.
  • After 0.3.0, every version that changesets computes is above 0.2.0. The problem cannot happen again, so no guard is added.

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-run in packages/vecstore-sdk reports vecstore-sdk-0.3.0.tgz.
  • npm view vecstore-sdk@0.3.0 returns E404 No match found for version 0.3.0. The time map of the package lists 0.2.0 but not 0.3.0.

Checklist

  • Tests have been added or updated. Not applicable: only the version changes.
  • Documentation has been added or updated. Not applicable. The site changelog entry for 0.3.0 is a separate pull request.
  • A changeset has been added for vecstore-sdk. Not applicable: a changeset would bump the version again. This pull request has the skip-changeset label.
  • I have reviewed this pull request myself

Summary by CodeRabbit

  • Chores
    • Updated the vecstore SDK package version to 0.3.0.
  • Documentation
    • Updated the changelog’s current release heading to 0.3.0. The release notes remain unchanged.

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.
@PunGrumpy PunGrumpy added the skip-changeset The pull request needs no release note label Nov 14, 2026
@vercel

vercel Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
vecstore-sdk Ready Ready Preview Nov 14, 2026 6:36pm UTC

@changeset-bot

changeset-bot Bot commented Nov 14, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2558fa0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The package version and current changelog release heading change from 0.2.0 to 0.3.0. The release notes remain unchanged.

Changes: Release metadata

Layer / File(s) Summary
Align release version metadata
packages/vecstore-sdk/package.json, packages/vecstore-sdk/CHANGELOG.md
The package version and changelog release heading change from 0.2.0 to 0.3.0.

Estimated code review effort: 1 (Trivial) | ~4 minutes

Change: Other

Merge Risk: Minimal · up to 2558f

This is a version-only bump to 0.3.0, so scan and unwrap can be published after the earlier 0.2.0 publish was rejected. It has no runtime effect, and publishing happens only through the manual Release workflow. It is ready to merge.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the change: the vecstore-sdk version is set to 0.3.0 instead of 0.2.0. The raw summary and objectives confirm that package.json and the top CHANGELOG.md heading change from 0.2.0 to 0.…
Description check Passed The description follows the template. Background explains why the change is needed and links the failed run. Summary states the version changes and the publish path. Verification names the commands ru…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title names the change: the vecstore-sdk version is set to 0.3.0 instead of 0.2.0. The raw summary and objectives confirm that package.json and the top CHANGELOG.md heading change from 0.2.0 to 0.3.0. The title is specific and matches the main change. The 'chore(release)' prefix is a conventional-commit style prefix and is acceptable.

Full details: Description check

Explanation

The description follows the template. Background explains why the change is needed and links the failed run. Summary states the version changes and the publish path. Verification names the commands run and their results. Checklist items are present, with reasons given for items marked not applicable. The author explains why no changeset is added, which fits the template's changeset item. Some checkboxes are unchecked, but each has a stated reason.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

A rabbit checks the version line,
Then finds the notes still neat and fine.
Two labels now say point three,
The release is set for all to see.
I hop along beneath the moon,
With tidy numbers in tune.

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 0c3afdbd-b992-4e90-a5b7-ac17a25b326a
Commits

Reviewing files that changed from the base of the PR and between d415e1d and 2558fa0.

Files selected for processing: 2

  • packages/vecstore-sdk/CHANGELOG.md
  • packages/vecstore-sdk/package.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Recent review details

Context from checks skipped due to timeout: 1

  • GitHub Check: CodeRabbit
Additional comments: 1

packages/vecstore-sdk/package.json: 1

3-3: Data Integrity & Integration

The manual Release run does not require a changeset to publish 0.3.0.

The non-snapshot path calls bun run release, which runs changeset publish after check:release. changeset publish publishes the version in each package's package.json when the registry does not already have it. It does not depend on pending changeset files. This PR does not need a changeset for the manual run to publish vecstore-sdk@0.3.0.

@pkg-pr-new

pkg-pr-new Bot commented Nov 14, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/vecstore-sdk@92

commit: 2558fa0

@PunGrumpy
PunGrumpy merged commit 72415eb into main Nov 14, 2026
14 checks passed
@PunGrumpy
PunGrumpy deleted the chore/release-0-3-0 branch November 14, 2026 18:39

This branch was successfully deployed

1 active deployment
Preview — 2558fa05 Deployed Nov 14, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changeset The pull request needs no release note

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant