Skip to content

feat: 7-day release quarantine for tool dependencies; 3 days for vulnerability fixes - #23

Open
cacack wants to merge 2 commits into
mainfrom
feat/release-age-quarantine
Open

cacack wants to merge 2 commits into
mainfrom
feat/release-age-quarantine

Conversation

@cacack

@cacack cacack commented Nov 18, 2026

Copy link
Copy Markdown
Owner

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)

  • mise's minimum_release_age defaults to 24h. Every committed uv.lock had exclude-newer exactly 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.
  • Now 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.
  • Verified locally: make mise-lock leaves the existing locks unchanged. Deleting yamllint's uv.lock and re-locking wrote exclude-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.minimumReleaseAge was null. 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.
  • 3 days still lands fixes quickly but gives the community time to catch it.

README's Supply-Chain Defenses table updated for both.

Known trade-offs

  • A tool bump whose dependencies need a release newer than 7 days won't resolve at lock time. If that happens, override with the per-tool minimum_release_age option.
  • gcloud (no release dates) and the zsh plugin commits (monthly, reviewed) remain outside the release-age quarantine, as before.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CSVrYV8Q2U4YTwnnLKZJqU

cacack and others added 2 commits November 17, 2026 19:50
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant