chore(ci): upgrade @semantic-release/npm to v13 for OIDC support#423
Merged
Conversation
|
🎉 This PR is included in version 4.0.4 🎉 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.
Chore: upgrade @semantic-release/npm to v13 for OIDC support
Summary
@semantic-release/npm@^13.1.5as an explicit devDependency to override the v12 transitive dependencyWhy
After switching to OIDC trusted publishing (merged in the previous PR), releases were failing with:
@semantic-release/npmv12 hard-requiresNPM_TOKENand has no awareness of OIDC. v13 added native OIDC support. Sincesemantic-releasepulls in v12 transitively, an explicit override is needed untilsemantic-releaseupdates its own peer dependency range.