Skip to content

fix(renovate): extract global defaults, 1-day trusted stabilization#151

Merged
JacobPEvans merged 2 commits intomainfrom
fix/renovate-global-defaults
Apr 1, 2026
Merged

fix(renovate): extract global defaults, 1-day trusted stabilization#151
JacobPEvans merged 2 commits intomainfrom
fix/renovate-global-defaults

Conversation

@JacobPEvans
Copy link
Copy Markdown
Owner

Summary

  • Extract automergeType, automergeStrategy, and minimumReleaseAge to top-level
    defaults — eliminates repetition across 8 rules
  • Reduce trusted org stabilization from 3 days to 1 day
  • Set global minimumReleaseAge: "3 days" default for untrusted packages
  • Group all global config (platformAutomerge, automergeType, automergeStrategy,
    minimumReleaseAge, timezone) at the top of the file

Changes

Setting Before After
automergeType / automergeStrategy Repeated in 8 rules Top-level default, inherited
Trusted org stabilization 3 days 1 day
Global minimumReleaseAge (none) 3 days default
Per-rule minimumReleaseAge: "3 days" Explicit in 4 rules Removed (inherits global)

Net: -30 lines, +13 lines — DRYer and more maintainable.

Follow-up to #150.

Test plan

  • Verify JSON validates (python3 -m json.tool renovate-presets.json)
  • Confirm inheriting repos need zero changes
  • Verify trusted org PRs use 1-day stabilization
  • Verify untrusted packages default to 3-day stabilization

🤖 Generated with Claude Code

…zation to 1 day

Move automergeType, automergeStrategy, and minimumReleaseAge to top-level
defaults so per-rule config only needs overrides. Trusted orgs stabilization
reduced from 3 days to 1 day; untrusted packages inherit 3-day global default.

(claude)
Copilot AI review requested due to automatic review settings April 1, 2026 13:58
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Refactors the org-wide Renovate preset to reduce repetition by moving shared automerge defaults to the top level, while adjusting stabilization timings (trusted orgs: 1 day; default: 3 days).

Changes:

  • Extract automergeType, automergeStrategy, and minimumReleaseAge into top-level defaults and remove per-rule duplicates.
  • Reduce trusted-organization minimumReleaseAge from 3 days to 1 day.
  • Group global configuration keys together at the top of the preset.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Lock file maintenance updates existing constraints, not new versions —
no stabilization period needed. Without this override, the global 3-day
default would unnecessarily delay lock file PRs.

(claude)
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the Renovate configuration to enhance maintainability and reduce redundancy. It centralizes common automerge and release stabilization settings, applies a shorter stabilization period for trusted dependencies, and sets a global default for untrusted packages, resulting in a cleaner and more efficient configuration.

Highlights

  • Configuration Refactoring: Extracted automergeType, automergeStrategy, and minimumReleaseAge to top-level defaults, significantly reducing repetition across eight individual Renovate rules.
  • Trusted Package Stabilization: Reduced the stabilization period for trusted organization packages from 3 days to 1 day, allowing for quicker integration of updates from known sources.
  • Global Untrusted Package Default: Established a global default minimumReleaseAge of "3 days" for untrusted packages, ensuring a consistent stabilization period for less familiar dependencies.
  • Configuration Organization: Consolidated all global Renovate configuration settings, including platformAutomerge, automergeType, automergeStrategy, minimumReleaseAge, and timezone, at the top of the renovate-presets.json file for improved readability and maintainability.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.


Config refactored, Defaults now reign, clean and clear, Bots merge with new speed.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@JacobPEvans JacobPEvans merged commit c9b875a into main Apr 1, 2026
2 checks passed
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