This repository was archived by the owner on Apr 21, 2026. It is now read-only.
fix(ci): use actions/setup-node directly for npm publish auth#44
Merged
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem
The
Publish to npmworkflow has been failing since v0.6.0 withENEEDAUTH. The custom composite actionForge-Space/.github/.github/actions/setup-node@maindoesn't acceptregistry-urlas an input, so the.npmrcfile for npm authentication is never created.Fix
Use
actions/setup-node@v6directly in the publish job (matching the pattern in@forgespace/core's working publish.yml) instead of the custom composite action. This ensuresregistry-urlis properly forwarded, creating the.npmrcthatNODE_AUTH_TOKENneeds.Verification
After merge, re-tag v0.6.1 (or create v0.6.2) to trigger a publish workflow run.