fix: Update NPM and also node to ensure trusted publishing works#490
Merged
lwasser merged 3 commits intoall-contributors:mainfrom Mar 9, 2026
Merged
fix: Update NPM and also node to ensure trusted publishing works#490lwasser merged 3 commits intoall-contributors:mainfrom
lwasser merged 3 commits intoall-contributors:mainfrom
Conversation
Member
Author
|
Sigstore does seem to be working to this is a specific to NPM piece that i can't seem to test locally and must test here. So sorry about the flood of notifications to anyone seeing all of this. |
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.
I wish there was another way to test this - it looks like node v22.x ships with npm 10.x but you need 11.x for trusted publishing to work.
I found a few examples of this in github issues and prs and also this post.
So this updates those items to see if the handshake will then work as expected.
I have triple checked permissions at this point.
What:
Why:
How:
Checklist: