Skip to content

chore: schedule renovate updates once a month - #88

Merged
ahal merged 1 commit into
mozilla-releng:mainfrom
ahal:ahal/push-ysvpvqxtqmns
May 8, 2026
Merged

ahal merged 1 commit into
mozilla-releng:mainfrom
ahal:ahal/push-ysvpvqxtqmns

Conversation

@ahal

@ahal ahal commented May 8, 2026

Copy link
Copy Markdown
Contributor

Most of our repos hardly ever receive commits, let alone releases. So updating their dependencies once a week is pointless and results in too much review load.

Once a month should be the default, and then repos where we should do it more frequently (like balrog, shipit and scriptworker-scripts), we can explicitly override this default.

@ahal ahal self-assigned this May 8, 2026
@ahal
ahal requested a review from a team as a code owner May 8, 2026 18:28
Most of our repos hardly ever receive commits, let alone releases. So
updating their dependencies once a week is pointless and results in too
much review load.

Once a month should be the default, and then repos where we should do it
more frequently (like balrog, shipit and scriptworker-scripts), we can
explicitly override this default.

I also ensured Github actions + pre-commit remain on an explicit once a
month schedule, so that if repos override the global config, these
CI-only bumps remain monthly (they don't impact the product).
@ahal
ahal force-pushed the ahal/push-ysvpvqxtqmns branch from da513cc to 372a1ba Compare May 8, 2026 18:32
@ahal
ahal merged commit 72f97d2 into mozilla-releng:main May 8, 2026
3 checks passed
@ahal
ahal deleted the ahal/push-ysvpvqxtqmns branch May 8, 2026 20:50
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.

2 participants