Skip to content

chore(renovate): set update schedule to monthly and group related updates together#34678

Open
g-husam wants to merge 5 commits into
mainfrom
g-husam-patch-1
Open

chore(renovate): set update schedule to monthly and group related updates together#34678
g-husam wants to merge 5 commits into
mainfrom
g-husam-patch-1

Conversation

@g-husam

@g-husam g-husam commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

This should minimize noise and disruption by creating update PRs every month, instead of as and when new versions become available, and by grouping together related version bumps and all patch version bumps.

See https://docs.renovatebot.com/presets-config/#configbest-practices for more info.

NOTE: Security updates should still be created immediately, as that is the default and can be customized via vulnerabilityAlerts in the json config.

The packageRules take precedence over inherited configs, so all patch updates will be grouped together. Beyond that, anything matching a group config will be grouped together (such as well known monorepos and other curated lists of packages).

Also updating to json5 format to legally allow for comments.

Validated locally:

$ npx --yes --package renovate -- renovate-config-validator
 INFO: Validating .github/renovate.json5
 INFO: Config validated successfully against 1 file(s)

g-husam added 2 commits June 29, 2026 17:17
This should minimize noise and disruption by creating update PRs every month, instead of as and when new versions become available.
@g-husam g-husam changed the title chore(renovate): set update schedule to monthly chore(renovate): set update schedule to monthly and group related updates together Jun 29, 2026
@g-husam g-husam marked this pull request as ready for review June 29, 2026 21:51
@g-husam g-husam requested review from a team and yoshi-approver as code owners June 29, 2026 21:51
Comment thread .github/renovate.json5
@aandreassa aandreassa added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jul 1, 2026
@aandreassa

Copy link
Copy Markdown
Contributor

We will merge this next week after the break!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Indicates a pull request not ready for merge, due to either quality or timing.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants