ci: Update renovate config for recent changes #703
Conversation
- Remove a group that's now in default config
- Added in: Group all GHA updates renovate-config#403
- TODO: Add rules for wrangler
.github/renovate.json
Outdated
| "allowedVersions": "<1.33.0" | ||
| }, | ||
| { | ||
| "matchBaseBranches": ["release/v4.0"], |
There was a problem hiding this comment.
Don't we need similar rules for release/v5.0?
There was a problem hiding this comment.
Yeah - for sure. This is essentially just a draft.
I'm using this branch (local to rancher repo) to run the Renovate ad-hoc. And ideally we should see PRs changing for the new rules. So far I have not had that success.
18f6d64 to
988aea4
Compare
988aea4 to
c71393f
Compare
|
Still no luck. Since I need to make my primary focus the SCC integration project, I may need to pass this off to another O&B teammate. @diogoasouza if you'd like to take this on that would be great. Potentially @pjbgf can assist you with the changes we would need customized for BRO. At a high level we simply want there to be renovate rules that respect branch restrictions as follows:
(I've excluded 4.0 as it will soon be removed as EoL anyway. So we can simply manage that branch by hand since most the renovate changes that it gets are too extreme of changes.) |
|
This is somehow linked to the idea to provide better mappings of Rancher Manager versions and specific dependency constraints. @diogoasouza I'm hoping to take a look at this in a |