chore(renovate): explicitly zero minimumReleaseAge to override Mend org layer#831
Merged
Merged
Conversation
… org layer Our config has no age gate, yet #816 fails artifacts on 'Minimum Release Age threshold' — the gate is injected by Mend's hosted org config, and an absent key does not override an inherited one. Set '0 days' explicitly so the repo value wins the config merge. If artifact errors persist after this, the gate is portal-global and must be cleared at developer.mend.io. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VZvom4Uzdoz5KbJeG8yhde
cailmdaley
added a commit
that referenced
this pull request
Jul 15, 2026
…se of every artifact failure (#841) The original Dependabot->Renovate migration config at .github/renovate.json5 was never removed when renovate.json was added at the root (#821/#822). Renovate (and Mend's cached config-file name) kept reading the old file, so weeks of edits to renovate.json were silently ignored while the json5's 14-day minimumReleaseAge broke every uv artifact update (renovate#41624). There was never an org-level Mend config layer — just this forgotten file. One config file now: renovate.json, carrying the low-noise design plus the json5 pieces worth keeping (ngmix pin guard, Actions digest pinning, OSV/ vulnerability automerge, majors behind dashboard approval). All age gates gone — fundamentally incompatible with uv-owned resolution. The '0 days' override from #831 is dropped as moot. Claude-Session: https://claude.ai/code/session_01VZvom4Uzdoz5KbJeG8yhde Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Why
Our
renovate.jsonhas had nominimumReleaseAgesince #822, yet #816 still fails artifact updates with "has not yet passed the Minimum Release Age threshold" (tqdm 4.68.4, hypothesis 6.156.6). The gate is therefore injected by Mend's hosted org-level config — and an absent key in repo config does not override an inherited one.What
One line:
"minimumReleaseAge": "0 days"at top level, so the repo value explicitly wins the config merge. Plus a description entry documenting the reasoning.Diagnostic either way
Upstream context: renovatebot/renovate#41624 (age gate fundamentally incompatible with uv-owned resolution) — still open, no movement since March.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VZvom4Uzdoz5KbJeG8yhde