fix(publish): unblock npm publish from changeset:verify#1032
Merged
Conversation
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The prepare lifecycle runs during npm publish, after the release workflow has already consumed all changesets, so changeset:verify always exited 1 and blocked publishing. Changeset presence is still enforced on PRs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: f9e3f2d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Storybook Preview Deployed✅ Preview URL: https://click-5ez1z3zdr-clickhouse.vercel.app Built from commit: |
hoorayimhelping
approved these changes
May 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
yarn changeset:verifyfrom thepreparescript sonpm publishdoesn't abort with "Couldn't locate any changeset." after the release workflow has consumed all changesets (failing run).patchchangeset for this fix.Test plan
Publish to npm with OIDCno longer fails on the changeset check.preparechecks (yarn test,yarn format,yarn lint,yarn circular-dependency:check) still run locally onyarn install.🤖 Generated with Claude Code