ci: npm >= 11.5.1 in the release job for trusted publishing - #8
Merged
Conversation
changeset publish hands off to the npm CLI, and the OIDC token exchange lives there from 11.5.1. Node 22's bundled npm 10 sent an unauthenticated PUT and the registry answered E404 for both packages. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
The 0.2.0 publish (run 34023340863) failed with E404 on PUT for both packages. Node 22 bundles npm 10; npm's OIDC exchange for trusted publishing needs 11.5.1+, so the PUT went out unauthenticated. Release job now uses Node 24 and upgrades npm explicitly. Merging re-runs Release on main and publishes 0.2.0.
Made with Cursor