Repository navigation
Conversation
Vulnerability fixes skipped minimumReleaseAge entirely: PR #7 adopted filelock 4.2.11 about 8 hours after its release. A compromised release presented as a fix would get the same fast track; 3 days gives the community time to catch it while still landing fixes quickly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CSVrYV8Q2U4YTwnnLKZJqU
mise's minimum_release_age defaults to 24h, so the Python and npm tools' transitive dependencies were locked from releases as new as a day old, while Renovate held the tools themselves for 7 days. Set it to 7d. Exact and already-locked versions are unaffected; it applies when a dependency graph is resolved (verified: re-locking yamllint wrote exclude-newer exactly 7 days back). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CSVrYV8Q2U4YTwnnLKZJqU
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.
Closes two gaps in the release-age quarantine, which gives the community time to catch a compromised release before it's adopted.
1. Tool dependencies: 24h → 7 days (
configs/.config/mise/config.toml)minimum_release_agedefaults to24h. Every committeduv.lockhadexclude-newerexactly 24h before its commit, so the Python and npm tools' transitive dependencies could be locked from day-old releases, even though Renovate held the tools themselves for 7 days.minimum_release_age = "7d". Per mise's docs it applies when a dependency graph is resolved (pypi and npm), not to exact or already-locked versions, so existing pins are untouched.make mise-lockleaves the existing locks unchanged. Deleting yamllint'suv.lockand re-locking wroteexclude-newer = 2026-11-11T00:49Z, exactly 7 days back. The test files were then restored.2. Vulnerability fixes: no wait → 3 days (
renovate.json)vulnerabilityAlerts.minimumReleaseAgewasnull. chore(deps): update dependency filelock to v4.2.1 [security] #7 adopted filelock 4.2.11 about 8 hours after release, so a compromised release presented as a security fix would get the same fast track.README's Supply-Chain Defenses table updated for both.
Known trade-offs
minimum_release_ageoption.🤖 Generated with Claude Code
https://claude.ai/code/session_01CSVrYV8Q2U4YTwnnLKZJqU