Skip to content

Conversation

@alan-agius4
Copy link
Contributor

Adds support for automatically modifying renovate.json to include newly created branches in the baseBranches array, when updateRenovateConfig is enabled.

@alan-agius4 alan-agius4 requested a review from devversion May 8, 2025 15:00
@alan-agius4 alan-agius4 added the action: review The PR is still awaiting reviews from at least one requested reviewer label May 8, 2025
@angular-robot angular-robot bot added the detected: feature PR contains a feature commit label May 8, 2025
@alan-agius4 alan-agius4 force-pushed the baseBranches branch 4 times, most recently from e54eaa7 to 3ca73c5 Compare May 9, 2025 06:59
const baseBranches = configJson.baseBranches;
if (!Array.isArray(baseBranches) || baseBranches.length !== 2) {
spinner.success(
yellow('Skipped updating Renovate config: "baseBranches" must contain exactly 2 branches.'),
Copy link
Member

Choose a reason for hiding this comment

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

Aren't there cases where we also want to update patch, rc and main?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good question. I think once the feature freeze begins, changes to the patch branch should be kept minimal to maintain stability, especially since it's heading to LTS soon.

Also, running Renovate on three branches would significantly increase runtime not to mention PRs will take longer to open due to rate limits.

Copy link
Member

Choose a reason for hiding this comment

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

Fair point

… branch

Adds support for automatically modifying `renovate.json` to include newly created branches in the `baseBranches` array, when `updateRenovateConfig` is enabled.
@devversion devversion merged commit d344104 into angular:main May 9, 2025
9 checks passed
@alan-agius4 alan-agius4 deleted the baseBranches branch May 9, 2025 22:02
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: review The PR is still awaiting reviews from at least one requested reviewer detected: feature PR contains a feature commit

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants