chore: patch bump all packages to recover the latest npm dist-tag - #37
Merged
Merged
Conversation
See PR #36 for the root cause: a prior release run's canary job no-op'd (zero pending changesets) and published the exact release versions under the canary tag, so the release job's publish of the same version strings under latest hit 409 Conflict from npm. No code changes here -- this changeset exists purely to produce fresh, publishable version numbers so the next release cycle can reach latest cleanly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012mMhPi1WBbxt6BxWJvJ6wD
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
Follow-up to #36. That PR fixed the root cause (canary job no-op'ing on zero pending changesets), but the six versions it already published under the
canarytag are stuck there — npm's Trusted Publishing OIDC only authorizes thepublishcommand, notdist-tag add(confirmed against npm/cli#8547, still open with no workaround), so there's no way to retag them without adding a classic npm token as a secret.Adds one changeset patch-bumping all 6 packages, no code changes. Merging the resulting Version Packages PR will publish fresh version numbers straight to
latestthrough the now-fixed pipeline — sidesteps the stuck dist-tag entirely instead of fighting it.Test plan
latestwith no 409s🤖 Generated with Claude Code
https://claude.ai/code/session_012mMhPi1WBbxt6BxWJvJ6wD
Generated by Claude Code