Repository navigation
fix(ci): avoid unresolved npm auth during cache setup - #28
Merged
Merged
Conversation
setup-node v7 no longer provides a dummy NODE_AUTH_TOKEN when registry-url is configured. During Yarn Classic cache discovery, the generated npm configuration therefore contains an unresolved token placeholder and aborts the release job before dependency installation. Remove registry-url from the Node setup step because this workflow publishes VSIX artifacts through vsce and ovsx rather than npm. Yarn caching remains enabled without creating an unused authenticated npm configuration. The exact yarn cache dir reproduction failed before the change and passed afterward with NODE_AUTH_TOKEN unset. actionlint, frozen install, lint, the zero-finding dependency audit, and all 7 extension-host tests also passed.
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.
Summary
Root cause
actions/setup-node v7 removed its dummy NODE_AUTH_TOKEN fallback. When registry-url is configured without a token, the action generates an npm configuration containing an unresolved token placeholder. Its Yarn Classic cache setup then runs yarn cache dir, which aborts before dependencies are installed.
This workflow publishes VSIX artifacts through vsce and ovsx; it does not publish an npm package, so registry-url was unnecessary.
Verification
README.md is unchanged.