fix: pass NODE_AUTH_TOKEN in publish workflow#97
Merged
Conversation
The npm publish has been failing since Dec 31 with "Access token expired or revoked". The token wasn't being explicitly passed to the changesets action. Also removes auto-merge of Version Packages PRs since GITHUB_TOKEN pushes can't trigger subsequent workflows.
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.
npm publish has been silently failing since December 31, 2025. Despite the repo sitting at 0.30.0+, the latest published version is still 0.29.1. The publish workflow was running without error—it just wasn't actually authenticating with npm because
NODE_AUTH_TOKENwas never being passed to the changesets action.The fix is a two-line change: pass
NODE_AUTH_TOKENalongsideGITHUB_TOKENin the publish step'senvblock.The second change removes the auto-merge step for Version Packages PRs. This was the root cause of the 1.0.0 release never shipping: GitHub Actions won't trigger further workflows when
GITHUB_TOKENpushes a commit, so auto-merging the Version Packages PR would complete silently without ever running publish. Removing auto-merge means the publish workflow runs properly when the Version Packages PR is merged manually.After merging, a fresh npm granular access token needs to be added as
NODE_AUTH_TOKENin the repo secrets, and then the Version Packages PR that changesets creates should be merged manually.