Repository navigation
Use npm trusted publishing for releases - #3
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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 release upload failed using the repository npm token. Switch publishing to GitHub Actions OIDC with Node 24, current checkout/setup-node actions, and job-scoped id-token permission. Remove NODE_AUTH_TOKEN and disable package-manager caching in release jobs.
Add manual dispatch accepting an existing release tag so v0.2.4 can be published using the corrected workflow without rewriting its tag. Verify that the checked-out package version matches the requested tag before upload.
npm requires a matching trusted publisher for Marcisbee/messagepipe, workflow publish.yml, with direct publishing allowed and no environment name. End-to-end verification will use the existing v0.2.4 release after merge.