Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

renovate: Use allowedVersions to limit updates to stable branches #1244

Merged
merged 1 commit into from
Oct 11, 2023

Conversation

chancez
Copy link
Contributor

@chancez chancez commented Oct 10, 2023

matchUpdateTypes is the wrong option for limiting updates in the stable branch. When I wrote this config, it was based off Cilium's config, which I looked at, and has since changed to using allowedVersions. It seems we're all slowly learning the lesson of how to correctly configure renovate. Ref #1239 (comment)

Signed-off-by: Chance Zibolski <chance.zibolski@gmail.com>
@chancez chancez added 🧹 kind/cleanup This includes no functional changes. 🤖 area/CI Impacts the testing / continuous integration testing of the project. labels Oct 10, 2023
@chancez chancez self-assigned this Oct 10, 2023
@chancez chancez requested a review from a team as a code owner October 10, 2023 22:38
@chancez chancez requested review from lambdanis and removed request for a team October 10, 2023 22:38
@maintainer-s-little-helper maintainer-s-little-helper bot added dont-merge/needs-release-note-label PR is blocked until the release note is set labels Oct 10, 2023
@chancez
Copy link
Contributor Author

chancez commented Oct 10, 2023

@aanm mentioned we could also still use matchUpdateTypes, but only on major/minor and then set enabled: false, as it's done here: https://github.com/cilium/cilium/blob/main/.github/renovate.json5#L436-L447

The approach I've taken is a bit more explicit, and will require changing the Go/Alpine versions as we update the matchBaseBranches. The approach he's mentioned is less explicit, but basically would only require us to update the matchBaseBranches. Each has pros/cons. I'm open to suggestions on which way we would like to do it.

@rolinh rolinh added the release-note/misc This PR makes changes that have no direct user impact. label Oct 11, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label PR is blocked until the release note is set label Oct 11, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Oct 11, 2023
@rolinh rolinh merged commit 47bdfe2 into main Oct 11, 2023
5 checks passed
@rolinh rolinh deleted the pr/chancez/renovate_stable_updates branch October 11, 2023 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤖 area/CI Impacts the testing / continuous integration testing of the project. 🧹 kind/cleanup This includes no functional changes. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants