chore: automerge Renovate lock file maintenance - #872
Merged
Conversation
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.
lockFileMaintenance is its own Renovate update type, not covered by the minor/patch/pin/digest automerge rule, so the weekly lock-refresh PR sat unmerged since July while Dependabot alerts piled up. This adds
automerge: truetolockFileMaintenanceso it merges on green CI like the rest.Also gates python version bumps behind dashboard approval: Renovate classes base-image bumps like 3.12→3.14 as "minor" rather than "major", so they weren't caught by the major-only approval rule and instead produced an immortal, perpetually-open PR (#866). We're staying on 3.12 deliberately; a python bump now needs an explicit dashboard tick.
🤖 Generated with Claude Code