-
Notifications
You must be signed in to change notification settings - Fork 36
[release/v1.3] sync changes from main #797
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
Merged
vardhaman22
merged 21 commits into
rancher:release/v1.3
from
vardhaman22:v1.3/sync-changes
Apr 7, 2025
Merged
[release/v1.3] sync changes from main #797
vardhaman22
merged 21 commits into
rancher:release/v1.3
from
vardhaman22:v1.3/sync-changes
Apr 7, 2025
Conversation
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
Signed-off-by: Paulo Gomes <[email protected]>
Signed-off-by: Paulo Gomes <[email protected]>
Signed-off-by: Paulo Gomes <[email protected]>
Signed-off-by: Paulo Gomes <[email protected]>
This ensure that main is always kept up to date, and backport branches receive security updates, while keeping PR noise to a minimum. The backport renovate will run fortnighly, to align with releases. Signed-off-by: Paulo Gomes <[email protected]>
The side effect of having two different Renovate configurations is that one will always close all the PRs it would not create. To avoid unnecessary noise this change split the schedules into 2. During the first 2 thirds of the month, run Renovate against the development branch. On the last third of the month, run it against the backport branches. Signed-off-by: Paulo Gomes <[email protected]>
Ensures that the core configuration focuses on keeping the development branch updated, while also proposing security fixes for backporting branches. The core configuration is scheduled for Tuesdays and Thursdays only. The backporting schedule is disabled, as its execution closes open PRs by a separate configuration (e.g. the core config). Signed-off-by: Paulo Gomes <[email protected]>
Signed-off-by: Paulo Gomes <[email protected]>
Signed-off-by: Paulo Gomes <[email protected]>
Signed-off-by: Paulo Gomes <[email protected]>
The changes add support for execution in forks and easier to set fields. Signed-off-by: Paulo Gomes <[email protected]>
andypitcher
approved these changes
Apr 7, 2025
pjbgf
approved these changes
Apr 7, 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.
similar to #796 for v1.3