ci(renovate): Automerge minor updates if all tests pass

[MaxymVlasov]

"Automerge" mean without human review

Can be merged after #821 (need to require check from pull_request event)

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Improved the automated dependency merge configuration to enhance the update process. Now, updates for minor, patch, and digest changes go through a more rigorous review process, including automated status checks and a pull request step. These changes ensure smoother integrations and maintain overall application quality. This update delivers a more reliable and consistent update workflow.

Walkthrough

The pull request updates the Renovate configuration in .github/renovate.json5 by expanding the extends array. The original single entry is now complemented with additional automerging settings. These new entries enable automerging for patch and minor upgrades, enforce that all status checks pass before merging, support digest upgrades, and require opening a pull request prior to automerging. The changes adjust the conditions under which Renovate automerges dependency updates.

Changes

File	Change Summary
.github/renovate.json5	Extended the extends array from one entry ("local>SpotOnInc/renovate-config") to include automerge settings: :automergeMinor, :automergeRequireAllStatusChecks, :automergeDigest, and :automergePr.

Sequence Diagram(s)

sequenceDiagram
  participant R as Renovate
  participant T as Test Suite
  participant GH as GitHub

  R->>R: Load renovate.json5 configuration
  R->>T: Run tests for dependency update candidate
  T-->>R: Return test results
  alt Tests pass
    R->>R: Evaluate update type (minor, patch, digest)
    alt ":automergePr" enabled
      R->>GH: Open pull request for update
      GH-->>R: PR created and status checks initiated
    else
      R->>GH: Automerge update directly if all status checks pass
      GH-->>R: Update merged
    end
  else
    R-->>GH: Do not merge update
  end

Loading

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1d67ef3 and 12984dc.

📒 Files selected for processing (1)

• .github/renovate.json5 (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (10)

• GitHub Check: 🧪 Tests / pytest@🐍3.9@windows-2025
• GitHub Check: 🧪 Tests / pytest@🐍3.13@windows-2025
• GitHub Check: 🧪 Tests / pytest@🐍3.13@macos-14
• GitHub Check: 🧪 Tests / pytest@🐍3.13@macos-13
• GitHub Check: 🧪 Tests / pytest@🐍3.12@windows-2025
• GitHub Check: 🧪 Tests / pytest@🐍3.12@macos-14
• GitHub Check: 🧪 Tests / pytest@🐍3.11@windows-2025
• GitHub Check: 🧪 Tests / pytest@🐍3.10@windows-2025
• GitHub Check: 🧪 Tests / pytest@🐍3.10@macos-14
• GitHub Check: pre-commit

🔇 Additional comments (2)

.github/renovate.json5 (2)

3-13: LGTM! Well-structured automerge configuration with proper safety measures.

The configuration is well-organized with clear comments and documentation links. The order of presets is logical, starting with base config and progressively adding automerge rules with appropriate safety checks.

Key benefits:

• Automated updates for minor versions reduce maintenance overhead
• Required status checks ensure stability
• PR requirement maintains visibility and control

---

7-8:

Details

❓ Verification inconclusive

Verify that all critical status checks are properly configured.

The :automergeRequireAllStatusChecks preset is a crucial safety measure. Ensure that all necessary status checks (tests, linting, security scans, etc.) are properly configured in your repository settings.

---

🏁 Script executed:

#!/bin/bash
# Description: Check repository's required status checks configuration

# List branch protection rules and their required status checks
gh api repos/{owner}/{repo}/branches/main/protection \
  --jq '.required_status_checks.checks[] | {context: .context, app_id: .app_id}'

Length of output: 356

---

Ensure Critical Status Checks Are Configured Correctly

The preset :automergeRequireAllStatusChecks is intended to ensure that all required status checks pass before automerging. Our verification command for branch protection settings returned a permission error ("Resource not accessible by integration", HTTP 403), making it inconclusive whether all critical checks (e.g., tests, linting, security scans) are properly enforced.

• Action Required: Manually verify via GitHub repository settings that branch protection rules include all necessary status checks.
• Suggestion: Check if integration permissions need adjusting to allow automated inspection in the future.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[antonbabenko]

This PR is included in version 1.97.4 🎉