Add release-2.2 branch to the renovate config#924
Merged
adamwg merged 1 commit intocrossplane:mainfrom Feb 9, 2026
Merged
Conversation
Signed-off-by: Adam Wolfe Gordon <awg@upbound.io>
phisco
approved these changes
Feb 9, 2026
jbw976
reviewed
Feb 9, 2026
Member
jbw976
left a comment
jbw976
left a comment
There was a problem hiding this comment.
i'm wondering if there's some trickiness we need to do here also now that we have nix. IIRC one of the config files had a blanket wildcard for all release branches, assuming that they all still have earthly, but now with the v2.2 release branch that's not true - release-2.2 has nix. can you look at that? 🤔
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
3 participants
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.
Description of your changes
Per the release checklist in crossplane/release#63, add release-2.2 to the base branches for renovate.
I have:
- [ ] Run./nix.sh flake checkto ensure this PR is ready for review.- [ ] Added or updated unit tests.- [ ] Linked a PR or a docs tracking issue to document this change.- [ ] Addedbackport release-x.ylabels to auto-backport this PR.