fix(ci): 🐛 Skip lifecycle scripts during npm publish in release workflow #30
Conversation
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
The `publish` script in package.json (`node scripts/publish.js`) is designed for local publishing and expects `NPM_TOKEN` env var, but the workflow sets `NODE_AUTH_TOKEN`. Adding `--ignore-scripts` avoids triggering the local publish script, since the workflow already handles version setting, dependency adjustment, and building independently. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
--ignore-scriptsflag tonpm publishin the release workflow to prevent triggering the localpublishlifecycle script (scripts/publish.js)NPM_TOKENenv var, but the workflow setsNODE_AUTH_TOKEN, causing the publish step to fail with "NPM_TOKEN not found"Root Cause
package.jsondefines"publish": "node scripts/publish.js"as a lifecycle script. Whennpm publishruns in CI, npm automatically executes this script first. The script checks forprocess.env.NPM_TOKEN, but the workflow only setsNODE_AUTH_TOKEN(the standard env var for npm registry auth via.npmrc), resulting in the error.Test Plan
npm publishsucceeds without the lifecycle script interferencenpm run publishstill works as expected for local beta publishing🤖 Generated with Claude Code