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

Increase number of renovate bot PRs #1615

Merged
merged 1 commit into from
Jun 27, 2024

Conversation

abaguas
Copy link
Collaborator

@abaguas abaguas commented Jun 26, 2024

Since #1610 was merged the number of PRs created by renovate increased, as bumps of libraries on version 0.x are handled in a dedicated PR. The maximum number of concurrent PRs is 5 which results in rate-limiting: #1048. The proposal is to increase it to 15 so that we can see and tackle the PRs containing potential breaking changes.

In addition, the update all non-major dependencies group should very rarely contain breaking changes (#1052) so I propose to turn on automerge (if the pipeline is green ofc). This should save the maintainers some precious minutes.

Since k8gb-io#1610 was merged the number of PRs created by renovate increased, as bumps of libraries on version 0.x are handled in a dedicated PR.
The maximum number of concurrent PRs is 5 which results in rate-limiting: k8gb-io#1048. The proposal is to increase it to 15 so that we can see and tackle the PRs containing potential breaking changes.

In addition, the `update all non-major dependencies` group should very rarely contain breaking changes (k8gb-io#1052) so I proposal to turn on automerge (if the pipeline is green ofc). This should save the maintainers some precious minutes.

Signed-off-by: abaguas <[email protected]>
@ytsarev
Copy link
Member

ytsarev commented Jun 26, 2024

@k0da @kuritka automerge is brave, I would appreciate your thumbs up for this one 👍

@kuritka
Copy link
Collaborator

kuritka commented Jun 26, 2024

@ytsarev,

I understand that passing tests give us a certain kind of security I'm just not sure with dependencies mentioned below (at least the first three or four are better to bump at once). For the rest of dependencies in main go.mod and terratests I'm 100% with @abaguas.

	k8s.io/api v0.26.3
	k8s.io/apimachinery v0.26.3
	k8s.io/client-go v0.26.3
	sigs.k8s.io/controller-runtime v0.14.5

@abaguas
Copy link
Collaborator Author

abaguas commented Jun 26, 2024

@ytsarev,

I understand that passing tests give us a certain kind of security I'm just not sure with dependencies mentioned below (at least the first three or four are better to bump at once). For the rest of dependencies in main go.mod and terratests I'm 100% with @abaguas.

	k8s.io/api v0.26.3
	k8s.io/apimachinery v0.26.3
	k8s.io/client-go v0.26.3
	sigs.k8s.io/controller-runtime v0.14.5

The auto-merge would affect only the "all non-major dependencies" group. The libraries you mentioned would still need a manual merge.

@kuritka
Copy link
Collaborator

kuritka commented Jun 26, 2024

correct, thx. Than I'm fine with that.

@kuritka kuritka self-requested a review June 26, 2024 14:29
@kuritka
Copy link
Collaborator

kuritka commented Jun 26, 2024

current controller-runtime is v0.14.5 , while v0.15.0 contains breaking changes. v0.18.x is latest now, but probably wouldn't pass tests / building.

@abaguas
Copy link
Collaborator Author

abaguas commented Jun 26, 2024

current controller-runtime is v0.14.5 , while v0.15.0 contains breaking changes. v0.18.x is latest now, but probably wouldn't pass tests / building.

@kuritka If you think it would make our life easier we can enable separateMultipleMinor. This would create one PR per minor bump and would all us to tackle the breaking changes one minor a time, instead of going directly from 0.14.x to 0.18.y.
We could match this rule only to the packages you mentioned:

	k8s.io/api v0.26.3
	k8s.io/apimachinery v0.26.3
	k8s.io/client-go v0.26.3
	sigs.k8s.io/controller-runtime v0.14.5

@abaguas
Copy link
Collaborator Author

abaguas commented Jun 27, 2024

I would be happy to merge this one already, we can check further improvements later if necessary.

Copy link
Collaborator

@kuritka kuritka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's try to merge it as it was planned originally. If there were problems with these dependencies, we could ignore them I guess.

Copy link
Member

@ytsarev ytsarev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for discussion, merging in

@ytsarev ytsarev merged commit 85c5c7e into k8gb-io:master Jun 27, 2024
9 checks passed
abaguas added a commit to abaguas/k8gb that referenced this pull request Jun 30, 2024
In k8gb-io#1615 auto merge was enabled for [all non-major dependencies](k8gb-io#1052 (comment)). However, the PR cannot be merged without an approving review.
The missing piece would be the following app: https://github.com/apps/renovate-approve. It would approve all PRs created by the renovate bot that have auto merge enabled. Unfortunately, it cannot do it for projects that have CODEOWNERS setup, which is our case:
> Important note: Due to a GitHub limitation, it is not possible to assign any app like this one as a CODEOWNER, so unfortunately this bot won't work that way if you have CODEOWNERS set up.

Since auto merge does not work this PR removes the configuration to avoid any confusion

Signed-off-by: abaguas <[email protected]>
ytsarev pushed a commit that referenced this pull request Jul 2, 2024
In #1615 auto merge was enabled for [all non-major dependencies](#1052 (comment)). However, the PR cannot be merged without an approving review.
The missing piece would be the following app: https://github.com/apps/renovate-approve. It would approve all PRs created by the renovate bot that have auto merge enabled. Unfortunately, it cannot do it for projects that have CODEOWNERS setup, which is our case:
> Important note: Due to a GitHub limitation, it is not possible to assign any app like this one as a CODEOWNER, so unfortunately this bot won't work that way if you have CODEOWNERS set up.

Since auto merge does not work this PR removes the configuration to avoid any confusion

Signed-off-by: abaguas <[email protected]>
@abaguas abaguas deleted the renovate/automerge branch July 9, 2024 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants