You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Set Renovate minimum release ages for dependencies and security fixes #2164
Update renovate.json5 so regular dependency updates wait 10 days, while security/vulnerability-fix updates wait 1 day. Configure the security override through vulnerabilityAlerts.minimumReleaseAge, since Renovate otherwise defaults vulnerability alert updates to minimumReleaseAge: null.
Docker image updates also need to tolerate missing release timestamps; otherwise they can remain pending indefinitely. Add this package rule:
{// Registries without release timestamps would otherwise leave Docker// updates pending indefinitely."description": "Allow container updates without release timestamp","matchDatasources": ["docker",],"minimumReleaseAgeBehaviour": "timestamp-optional",},
What is the value to the end user? (why is it a priority?)
A 10-day delay reduces the risk of adopting a newly published compromised release, while security fixes are delayed by only one day. Docker updates without release timestamps won't get stuck indefinitely.
How will we know we have a good solution? (acceptance criteria)
Regular dependency updates observe a 10-day minimum release age.
Security/vulnerability-fix updates observe a 1-day minimum release age.
Docker updates with no release timestamp are still eligible; timestamped Docker releases observe the configured age.
Lock file maintenance remains enabled without adding "minimumReleaseAge": null; Renovate excludes lockFileMaintenance updates from minimum-release-age checks.
Activity
Configure Renovate minimum release ages