Repository navigation
feat(renovate): fast-lane Foundry bumps in consumer repos - #80
Merged
Merged
Conversation
Foundry is our own repo, so the 7-day release hold only delayed our own fixes by a week or two. Foundry refs now skip the hold, get their own PR on any day, and automerge once the consumer's gate passes. They stay digest-pinned, so every bump still goes through the gate.
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.
Foundry refs skip the 7-day hold, get their own PR on any day, and automerge once the consumer's gate is green. Still digest-pinned, so a bad Foundry release fails one gated PR per repo instead of breaking every main at once.
Needs "Allow auto-merge" and required checks on the consumer repo, which tech-atlas already has.