Skip to content

Conversation

pjbgf and others added 24 commits April 7, 2025 11:50
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]>
The changes add support for execution in forks and easier to set
fields.

Signed-off-by: Paulo Gomes <[email protected]>
@vardhaman22 vardhaman22 marked this pull request as ready for review April 7, 2025 07:07
@vardhaman22 vardhaman22 requested review from a team as code owners April 7, 2025 07:07
@vardhaman22 vardhaman22 merged commit 8461590 into rancher:release/v1.4 Apr 7, 2025
8 checks passed
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