chore: pnpm release pushes its own tags - #64
Merged
Conversation
changeset tag creates tags but never pushes them, so every release ended with a manual `git push --tags` that is easy to forget — and the failure is silent: npm looks published and the repo just quietly lacks tags. 0.8.1's three tags were stranded that way and pushed by hand afterwards. Also records in CLAUDE.md that npm 2FA forces `pnpm release` into an interactive terminal; a non-interactive run dies with ERR_PNPM_OTP_NON_INTERACTIVE before publishing anything. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
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
1 participant
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.
changeset tagcreates the version tags but never pushes them, so every release ended with a manualgit push --tags. That step is easy to forget and the failure is silent — npm shows the packages published, and the repo simply lacks tags until someone notices.It has now bitten twice running. 0.8.1's three tags sat local-only after publish and were pushed by hand; the remote's newest tags were still 0.8.0 while npm already served 0.8.1.
package.json— thereleasescript gains&& git push --tags.CLAUDE.md— the release recipe drops the manual step, and records why the gap existed.While here,
CLAUDE.mdalso gains a note that npm 2FA forcespnpm releaseinto an interactive terminal. A non-interactive run dies withERR_PNPM_OTP_NON_INTERACTIVEat the first package, before publishing anything — which is exactly what happened cutting 0.8.1, and is worth knowing before an agent session tries it.No package change, so no changeset.
🤖 Generated with Claude Code