Pin npm to 10.x for OIDC trusted publishing#98
Merged
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.
The corepack step is still needed for unrelated reasons, but
npm@latest(currently 11.14) breaks OIDC trusted publishing — npm 11 returns ENEEDAUTH instead of falling through to OIDC when_authTokenresolves to empty.byoc publishes successfully via OIDC using its bundled Node 24 npm (~10.x, judging by the deprecated
always-authwarnings in its logs). Pinning to npm 10 here matches that working setup.Test plan