chore(deps): restrict Phase 1 to minimal lockfile maintenance without proactive Gemfile bumps#34759
Open
torreypayne wants to merge 2 commits into
Open
chore(deps): restrict Phase 1 to minimal lockfile maintenance without proactive Gemfile bumps#34759torreypayne wants to merge 2 commits into
torreypayne wants to merge 2 commits into
Conversation
torreypayne
added
the
do not merge
torreypayne
removed
the
do not merge
torreypayne
changed the title
quartzmo
requested changes
Jul 14, 2026
aandreassa
approved these changes
Jul 14, 2026
… proactive Gemfile bumps Restricts Renovate Phase 1 (`core handwritten gems lockfiles`) so that it prioritizes scheduled `Gemfile.lock` maintenance (`bundle lock --update`) while disabling proactive `Gemfile` dependency upgrades across the board (`matchDatasources: ["rubygems"] -> enabled: false`). Note: Even though proactive package updates (`rubygems`) are disabled, when `lockFileMaintenance` runs under Renovate's bundler manager, it can still trigger `Gemfile` constraint updates to synchronize out-of-date bounds (e.g., internal monorepo gems or dev utilities) with the refreshed `Gemfile.lock`.
torreypayne
force-pushed
the
chore/restrict-renovate-lockfiles-only
branch
from
af31b0c to
b48376c
Compare
aandreassa
approved these changes
Jul 14, 2026
…ockFileMaintenance
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Restricts Renovate Phase 1 (
core handwritten gems lockfiles) so that it prioritizes scheduledGemfile.lockmaintenance (bundle lock --update) while disabling proactiveGemfiledependency upgrades across the board (matchDatasources: ["rubygems"] -> enabled: false).Details
matchDatasources: ["rubygems"], enabled: falseacross the 9 Phase 1 gems (google-cloud-core,google-cloud-storage,google-cloud-pubsub,google-cloud-bigquery,google-cloud-errors,google-cloud-resource_manager,google-cloud-bigtable,google-cloud-logging,google-cloud-monitoring), Renovate will not open proactive version bump PRs (major,minor,patch) on a daily basis.lockFileMaintenance): Runs once every morning before 5am (schedule: ["before 5am"]) underrangeStrategy: "update-lockfile"to refreshGemfile.lockfiles across Phase 1 (core handwritten gems lockfiles).bundle lock --updateruns under Renovate's Bundler manager, Renovate does the absolute minimum necessary to maintain lockfiles without breaking builds—automatically keeping internal monorepo package bounds (connection-v1) and stale test/style utilities (minitest-reporters) synchronized insideGemfileif they drift from the refreshed lockfile.Gemfiledependency bumps across Phase 1, simply delete thematchDatasourcesexclusion rule from.github/renovate.json5.