[PunGrumpy]

Background

Verify Changesets fails on every release pull request. The changesets bot opens #60 from changeset-release/main, which deletes the changesets and bumps packages/*/package.json. The check then sees a package change with no changeset.

Summary

Skip the job when the head branch is changeset-release/main in this repository. The guard is the same one docker-doctor uses. Pull requests from forks with that branch name still run the check.

Verification

The failing run on #60 is the "Require a changeset for package changes" step. This pull request does not touch packages/** or .changeset/, so its own run is skipped by the path filter. The guard takes effect on the next push to #60.

Checklist

• Tests have been added or updated
• Documentation has been added or updated
• A changeset has been added for vecstore-sdk (run bun run changeset in the project root)
• I have reviewed this pull request myself

[vercel]

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

Project	Deployment	Actions	Updated
vecstore-sdk	Ready	Preview	Oct 26, 2026 2:08am UTC

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0297ffe

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]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 59 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

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: 06a89feb-6b21-49c2-8e61-dbc62f5fc7c4

Commits

Reviewing files that changed from the base of the PR and between 291dad2 and 0297ffe.

Files selected for processing: 1

• .github/workflows/verify-changesets.yml

• 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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[baymiai]

Security review: nothing to raise.

The new guard matches the stated intent: same-repo release PRs from changeset-release/main skip the check, while forks with that branch name still run it.

Reviewed at 0297ffe.

[pkg-pr-new]

Open in StackBlitz

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

commit: 0297ffe