chore(deps): automerge dependencies updates. #163
Merged
Conversation
This file contains 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
Updates renovate bot configuration to allow it to automerge PRs. Signed-off-by: José Guilherme Vanz <[email protected]>
viccuad
approved these changes
Jan 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Updates renovate bot configuration to allow it to automerge PRs. With this configuration renovate bot will:
@kubewarden/kubewarden-developers this is a initial proposal to enable automerge for dependencies updates for our policies. With this configuration the PRs will gradually be open and merged. By default, renovate bot creates 2 PR on hourly bases. Considering that the PR will be merge automatically, I do not think this is a problem. Furthermore, this way we do not overload our CI.
I believe we can leave this configuration running on this policy for a while to see if we are all happy with it. If this is the case, we can move this config to a repository to store the renovate configuration and point all the policies to it. Therefore, we do not need to update all the repositories manually.
Warning
We may want to set some requirements in the CI for all our policies to prevent bot merging policies with issues. I think we should set the tests as requirements.
Fix kubewarden/kubewarden-controller#801