fix(ci): release .npmrc to $HOME (no token in tree) - #83
Merged
Conversation
The first release run had the changesets "version packages" commit pick up the repo-root .npmrc (`?? .npmrc` → committed) — a token-leak risk once NPM_TOKEN is set. Write it to $HOME/.npmrc so it's never in the working tree the changesets action commits. (The run also failed because the repo's "Allow GitHub Actions to create and approve pull requests" setting is off — that's a repo setting to enable; the version step itself worked and bumped server/cli correctly.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UeVCwYURGVrm2TFtQmWB3s
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.
The release workflow's version commit was picking up the repo-root .npmrc. Write to $HOME instead. 🤖 Generated with Claude Code