Skip to content

Comments

fix: update renovate rules#1495

Open
gjtorikian wants to merge 2 commits intomainfrom
renovate-renovate
Open

fix: update renovate rules#1495
gjtorikian wants to merge 2 commits intomainfrom
renovate-renovate

Conversation

@gjtorikian
Copy link
Contributor

@gjtorikian gjtorikian commented Feb 20, 2026

Description

There's been some feedback that the renovate notifications are super noisy and can clog up GitHub. This PR is an attempt to trim down the noise by setting a few options:

  • schedule: ["every 3rd Tuesday"]: Renovate will only create/update branches once a month, on the 3rd Tuesday
  • rebaseWhen: "conflicted": only rebases when there are actual conflicts (not just when behind the base branch)
  • Major vs minor/patch vs digest separation — three packageRules entries:
    • Minor/patch are grouped into a single PR and automerged
    • Major and digest updates each get their own individual PRs with automerge disabled

The major v major/minor thing is so that Renovate doesn't open a PR per change—which, given the new cron scheduling, is likely to have some drift between packages—but rather, groups the PRs together into one.

digest is currently unused in this PR, but soon I'll open a PR to pin the GitHub Actions to a specific SHA, to tighten any potential security vulns that come up. These, too, are grouped into their own PRs, because we can't tell if the SHA updates will introduce breaking or non-breaking changes.

I removed pin because it does not seem to me that we would ever want a dependency frozen at a specific version, never to be updated.

Documentation

Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.

[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

- `schedule: ["every 2 weeks on Tuesday"]`: Renovate will only create/update branches every other Tuesday
- `rebaseWhen: "conflicted"`: only rebases when there are actual conflicts (not just when behind the base branch)
- Major vs minor/patch vs digest separation — three packageRules entries:
  - Minor/patch are grouped into a single PR  and automerged
  - Major and digest updates each get their own individual PRs with automerge disabled
@gjtorikian gjtorikian requested a review from a team as a code owner February 20, 2026 18:53
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 20, 2026

Greptile Summary

Updates Renovate configuration to reduce GitHub notification noise by implementing biweekly scheduling and improved dependency update grouping.

  • Schedules Renovate runs for every 2 weeks on Tuesday instead of continuous updates
  • Groups minor and patch updates into a single automerged PR to reduce noise
  • Separates major updates into individual PRs without automerge for manual review
  • Adds digest update handling (prepared for future GitHub Actions SHA pinning)
  • Removes pin from automerge types (using modern matchUpdateTypes syntax)
  • Sets rebaseWhen: "conflicted" to only rebase when necessary

Confidence Score: 5/5

  • This PR is safe to merge - it only modifies Renovate configuration with valid, well-structured settings
  • Configuration changes are syntactically correct using modern Renovate syntax, the scheduling and grouping strategy is sound for reducing notification noise, and there are no security or functional concerns with dependency management tooling updates
  • No files require special attention

Important Files Changed

Filename Overview
renovate.json Updates Renovate config to reduce notification noise with biweekly scheduling, groups minor/patch updates for automerge, and separates major/digest updates

Last reviewed commit: ffac40b

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

1 file reviewed, no comments

Edit Code Review Agent Settings | Greptile

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants