chore: RID-12099 - prepare for npm v12: drop always-auth via setup-node v6 - #24
Merged
Merged
Conversation
amit-schreiber-transmit
changed the title
amitblumshtien
approved these changes
Aug 27, 2026
…de v6 setup-node@v3's always-auth input unconditionally writes a bare, unscoped always-auth=<value> line to .npmrc whenever registry-url is set, regardless of the input's value. npm >=11.16 rejects always-auth in any form (removed in npm v12). setup-node@v6 dropped the always-auth input and its .npmrc writing entirely -- confirmed against its source, the registry-url/_authToken/ NODE_AUTH_TOKEN mechanism this workflow relies on is otherwise unchanged. The build job's setup-node call had always-auth: true but no registry-url, so it was already a no-op; removed for consistency with the other two calls in this file. ci.yml doesn't set registry-url or always-auth anywhere, so it isn't affected and is left untouched.
amit-schreiber-transmit
force-pushed
the
RID-12099-prepare-for-npm-v12
branch
from
August 27, 2026 08:21
c5124fb to
8c013e9
Compare
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
2 participants
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.
setup-node@v3's always-auth input unconditionally writes a bare, unscoped always-auth= line to .npmrc whenever registry-url is set, regardless of the input's value. npm >=11.16 rejects always-auth in any form (removed in npm v12). setup-node@v6 dropped the always-auth input and its .npmrc writing entirely -- confirmed against its source, the registry-url/_authToken/ NODE_AUTH_TOKEN mechanism this workflow relies on is otherwise unchanged. The build job's setup-node call had always-auth: true but no registry-url, so it was already a no-op; removed for consistency with the other two calls in this file. ci.yml doesn't set registry-url or always-auth anywhere, so it isn't affected and is left untouched.