fix: revert @semantic-release/npm to v12 to restore npm publish auth - #22
Merged
Conversation
@semantic-release/npm@13 uses OIDC for npm authentication, which is not configured for this package. v12 uses NPM_TOKEN which works with the existing GitHub secret. Also fixes 3 dev-only vulns in bundled npm were reintroduced, but these are dev-only (inside @semantic-release/npm's bundled npm) and do not affect runtime.
|
🎉 This PR is included in version 1.13.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Problema
@semantic-release/npm@13 usa OIDC per auth, non configurato su npmjs.com.
Fix