fix: update dependencies to have semantic-release working#5128
Merged
traefiker merged 1 commit intotraefik:masterfrom Apr 1, 2026
Merged
fix: update dependencies to have semantic-release working#5128traefiker merged 1 commit intotraefik:masterfrom
traefiker merged 1 commit intotraefik:masterfrom
Conversation
mmatur
changed the title
mmatur
force-pushed
the
fix/dep-upgrade
branch
7 times, most recently
from
2b1242a to
37e8dcd
Compare
mloiseleur
approved these changes
Apr 1, 2026
|
🎉 This PR is included in version 12.0.12-rc.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 12.0.12 🎉 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
3 participants
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.
Description
Context
Following PR #5126 (trusted publishing), @semantic-release/npm v13+ is required for provenance: true support. The major version upgrades of semantic-release plugins pulled in newer transitive dependencies that conflicted with Yarn's hardened mode + safe-chain's SAFE_CHAIN_MINIMUM_PACKAGE_AGE_HOURS=360 policy.
Yarn hardened mode re-resolves all packages from the registry on public PRs, but safe-chain filters out versions published less than 15 days ago from registry responses — making it impossible to pin all transitive dependencies (e.g., npm alone has 65+ direct deps). Disabling hardened mode lets Yarn trust the lockfile while safe-chain continues to protect against malicious packages on direct downloads.