fix: update renovate rules

[workos-sdk-automation]

Summary

Updates Renovate configuration to reduce noise and improve dependency management:

• Monthly schedule: Runs on the third Tuesday of the month before 12pm UTC
• Conflict-only rebasing: Only rebases PRs when they have conflicts
• Grouped minor/patch with automerge: Minor and patch updates are grouped together and automerged
• Separate major/digest PRs without automerge: Major and digest updates get their own PRs and require manual review

This aligns with the configuration in workos-node#1495.

[greptile-apps]

Greptile Summary

Replaces the minimal Renovate configuration with a more comprehensive setup aligned with the workos-node repository. Changes include a monthly schedule (third Tuesday before 12pm UTC), conflict-only rebasing, automerged minor/patch updates grouped together, and separate non-automerged PRs for major and digest updates.

• Uses config:base preset instead of the previous config:recommended (they are functionally equivalent as config:base is aliased to config:recommended, but the latter is the canonical name in current Renovate docs)
• Removes the $schema property which provided IDE validation support
• Package rules are well-structured: automerge for low-risk updates, manual review for major/digest changes

Confidence Score: 4/5

• This PR is safe to merge — it only modifies Renovate bot configuration with no impact on application code.
• Config-only change with no application code impact. Minor style concern about using the deprecated config:base alias instead of config:recommended, and removing the $schema for IDE validation. The package rules and scheduling logic are correct and well-structured.
• No files require special attention — this is a single configuration file change.

Important Files Changed

Filename	Overview
renovate.json	Renovate config replaced with monthly schedule, conflict-only rebasing, and grouped minor/patch automerge. Uses deprecated config:base preset alias instead of config:recommended, and drops $schema for IDE validation.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Renovate Bot Runs<br>3rd Tuesday Monthly] --> B{Check Update Type}
    B -->|minor / patch| C[Group into single PR<br>'minor and patch updates']
    B -->|major| D[Create separate PR]
    B -->|digest| E[Create separate PR]
    C --> F{Automerge enabled}
    F -->|Yes| G[Auto-merge PR]
    D --> H{Manual review required}
    E --> H
    H --> I[Await developer approval]
    J{PR has conflicts?} -->|Yes| K[Rebase PR]
    J -->|No| L[Leave PR as-is]

Loading

_{Last reviewed commit: d6b6d9b}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Consider using config:recommended preset

config:base was renamed to config:recommended in Renovate. While config:base still works as an alias, the Renovate docs now recommend using config:recommended as the canonical preset name. The previous config already used config:recommended. Was this intentional to align with workos-node, or an oversight?

Additionally, the $schema property ("$schema": "https://docs.renovatebot.com/renovate-schema.json") was removed. This provided IDE autocompletion and validation for the config file — consider keeping it.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}