Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature Request: Option to always stay X weeks out of date #3897
What would you like Renovate to be able to do?
Describe the solution you'd like
Describe alternatives you've considered
I think this is a good idea but never worked out a fool-proof approach. If v1.1.0 was 4 weeks old but v1.1.1 was 3 weeks and 6 days old, would you want a PR for v1.1.0 even though we can logically assume that v1.1.1 probably fixed a problem with v1.1.0? If so then you may end up with the opposite of what you were hoping - you've deployed a buggy/bad version.
If instead we changed the rule to say "only update when latest release is 4 weeks old" then if you get any project that releases more often then monthly then you'd never get a release.
I've also considered if we can use different "stability" periods depending on release type. e.g. for a major release, I might also think 4 weeks. For a minor release, maybe 1-2 weeks, and for a patch release maybe also 1 week. e.g. if a patch is released and no newer patch or release is out within a week, we can assume some level of stability.
FYI we're also working on the ability to communicate to you a confidence factor we have in releases, and that will be partly based on (a) aggregate test passes (all users) and (b) what % of users have already upgraded to a release. I think that the % upgrade is a good signal about the safeness of a release, assuming we observe no rollbacks.