Conversation
The 0.6.1 publish failed with E404: the NPM_TOKEN secret, created 2026-07-04, hit npm's 90-day cap on write tokens on 2026-10-02. With NPM_TOKEN unset, changesets/action writes no ~/.npmrc and pnpm 11's publish exchanges the job's OIDC token (id-token: write, already granted) for a short-lived npm token. Needs a trusted publisher configured on npmjs.com for @karnstack/reins; RELEASING.md says which. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why
The release run after merging Version Packages (#47) failed at publish:
Build and tests passed. npm answers a publish it won't authorize with 404. The
NPM_TOKENsecret was created 2026-07-04, and npm caps write tokens at 90 days, which ran out on 2026-10-02, the day of the run. 0.6.0 published fine with the same token on 2026-09-28. npm is also restricting tokens that bypass 2FA for direct publishing, so swapping in a new token would just put this off.What
release.yml: removeNPM_TOKENfrom the changesets step. With it unset,changesets/action@v1writes no~/.npmrcand logs "using npm trusted publishing".pnpm publish(11.9) trades the job's OIDC token for a short-lived npm token.id-token: writewas already granted for provenance.docs/RELEASING.md: dropNPM_TOKENfrom required secrets, document the trusted publisher entry and theE404it causes when missing.Merging pushes to
main, which runsreleaseand publishes 0.6.1. First, on npmjs.com →@karnstack/reins→ Settings → Trusted Publisher → GitHub Actions:karnstackreinsrelease.ymlThen delete the
NPM_TOKENrepo secret (optional; it's already dead).Test plan
releaserun logs "using npm trusted publishing", publishes@karnstack/reins@0.6.1, tags + GitHub release appear🤖 Generated with Claude Code