Skip to content

fix(renovate): fall back to the newest aged release instead of starving - #22

Merged
emkraan-deploy-bot[bot] merged 1 commit into
mainfrom
fix/renovate-flexible-release-age
Oct 3, 2026
Merged

emkraan-deploy-bot[bot] merged 1 commit into
mainfrom
fix/renovate-flexible-release-age

Conversation

@cmarko89

@cmarko89 cmarko89 commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Sets internalChecksFilter: "flexible" in the org Renovate preset.
  • Default strict makes Renovate consider only the newest release. Fast-release images (windmill, unpoller, honcho) never have a newest release older than minimumReleaseAge: 3 days, so they were silently never bumped. Windmill is 19 releases behind (1.803.0 vs 1.822.0) though 1.818.0 cleared the age gate on 2026-09-28.
  • flexible keeps the 3 day guardrail and proposes the newest release that has passed it.

Test plan

  • renovate-config-validator passes
  • Next before-6am Renovate run on homelab-stacks opens the docker image updates group with windmill, unpoller, honcho

🤖 Generated with Claude Code

With the default strict internalChecksFilter, Renovate only considers the
newest release of a dependency. For images that publish every one to three
days (windmill, unpoller, honcho) the newest release is always younger than
the 3 day minimumReleaseAge, so no update was ever proposed: windmill sat on
1.803.0 while 1.818.0 had been eligible for over a week. flexible keeps the
3 day guardrail but proposes the newest release that has cleared it.
@emkraan-deploy-bot
emkraan-deploy-bot Bot merged commit 4aa0936 into main Oct 3, 2026
2 checks passed
@emkraan-deploy-bot
emkraan-deploy-bot Bot deleted the fix/renovate-flexible-release-age branch October 3, 2026 13:58
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