chore(deps): widen Phase 1 lockfile maintenance coverage and schedule daily#34742
Merged
Conversation
Member
Author
|
@aandreassa wdyt about us testing this out? |
aandreassa
reviewed
Jul 9, 2026
aandreassa
approved these changes
Jul 10, 2026
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
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
Widens the Phase 1
Gemfile.lockRenovate automation coverage (matchFileNamesin.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
schedulefor 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
!google-cloud-.../**)."before 5am every day"(lockFileMaintenance.schedule).