Skip to content

chore(deps): widen Phase 1 lockfile maintenance coverage and schedule daily#34742

Merged
aandreassa merged 1 commit into
mainfrom
chore/widen-renovate-lockfile-coverage
Jul 10, 2026
Merged

chore(deps): widen Phase 1 lockfile maintenance coverage and schedule daily#34742
aandreassa merged 1 commit into
mainfrom
chore/widen-renovate-lockfile-coverage

Conversation

@torreypayne

Copy link
Copy Markdown
Member

Overview

Widens the Phase 1 Gemfile.lock Renovate automation coverage (matchFileNames in .github/renovate.json) to include 4 additional core wrapper gems:

  • google-cloud-resource_manager/**
  • google-cloud-bigtable/**
  • google-cloud-logging/**
  • google-cloud-monitoring/**

Additionally updates the schedule for lockfile maintenance from "before 5am on monday" to "before 5am every day" so we can validate automated daily lockfile generation and PR creation before proceeding with Phase 2 scale-out across remaining gems.

Details

  • Excludes these 4 additional gems from the negated non-Phase 1 exclusion rule (!google-cloud-.../**).
  • Adds these 4 additional gems to the Phase 1 core & handwritten lockfile generation rule.
  • Sets schedule to "before 5am every day" (lockFileMaintenance.schedule).

@torreypayne torreypayne requested review from a team and yoshi-approver as code owners July 9, 2026 23:35
@torreypayne

Copy link
Copy Markdown
Member Author

@aandreassa wdyt about us testing this out?

Comment thread .github/renovate.json
@aandreassa aandreassa merged commit 377f8a3 into main Jul 10, 2026
20 checks passed
@aandreassa aandreassa deleted the chore/widen-renovate-lockfile-coverage branch July 10, 2026 01:31
@github-actions github-actions Bot added the release-please:force-run To run release-please label Jul 10, 2026
@release-please release-please Bot removed the release-please:force-run To run release-please label Jul 10, 2026
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