chore: enforce pnpm minimumReleaseAge to align with renovate#116
Merged
Conversation
Add minimumReleaseAge: 10080 (7 days in minutes) to pnpm-workspace.yaml so pnpm itself refuses to install package versions younger than the same 7-day window renovate.json5 already enforces for PR creation. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
🎉 This PR is included in version 2.1.0 🎉 The release is available on GitHub release 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.
Summary
Add pnpm's
minimumReleaseAge: 10080(7 days, in minutes) topnpm-workspace.yamlso pnpm itself refuses to install package versions younger than the same 7-day windowrenovate.json5already enforces for PR creation (minimumReleaseAge: '7 days').This closes a gap where renovate gates PRs but local / CI
pnpm install(e.g. lockfile regeneration or adding a new dependency) could still pull just-published versions, leaving supply-chain risk on the table.pnpmis pinned to11.0.9viamise.toml, which supportsminimumReleaseAge(introduced in pnpm 10.16).renovate.json5to keep both values in sync if either is changed.pnpm install --frozen-lockfile(verified locally).References