fix(ci): npm 10 cannot do OIDC trusted publishing; pin npm@11 in release - #25
Merged
Conversation
changeset publish died with ENEEDAUTH (run 33205361374): the OIDC exchange for trusted publishers landed in npm CLI 11.5.1; Node 22 bundles npm 10.x, which falls back to classic auth and there is no classic auth by design. Pin npm@11 in the release job and stop caching its package manager on release builds. actionlint + prettier clean.
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.
changeset publish died with ENEEDAUTH (run 33205361374): the OIDC
exchange for trusted publishers landed in npm CLI 11.5.1; Node 22
bundles npm 10.x, which falls back to classic auth and there is no
classic auth by design. Pin npm@11 in the release job and stop caching
its package manager on release builds.
actionlint + prettier clean.