chore(deps): automate Gemfile.lock maintenance (phase 1)#34666
Open
torreypayne wants to merge 4 commits into
Open
chore(deps): automate Gemfile.lock maintenance (phase 1)#34666torreypayne wants to merge 4 commits into
torreypayne wants to merge 4 commits into
Conversation
Automate Gemfile.lock generation and periodic maintenance for compliance mandate https://b.corp.google.com/issues/509981628.
suztomo
reviewed
Jun 25, 2026
suztomo
left a comment
suztomo
left a comment
Member
There was a problem hiding this comment.
Would you familiarize yourself with this zizmor tool? go/github-zizmor-help?polyglot=github-com#local-scans-run-zizmor-on-your-cloudtop It tells fixes for GitHub actions.
…s per zizmor audit
Member
Author
Installed, ran, and fixes applied! Thanks for introducing me to the tool 👍🏿 |
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
This PR implements Phase 1 of the organization-wide compliance initiative to generate and maintain deterministic
Gemfile.lockfiles across Ruby client libraries (resolving b/509981628).For the full architectural strategy, throughput analysis, and multi-phase rollout cadence, please see the proposal document in Google Drive:
📄 Scale & Automate Dependency Security across Ruby Repositories (P1 Compliance)
Phase 1 Scope & Changes
Rather than attempting to generate and maintain ~880 lockfiles across
google-cloud-rubyin a single unmanageable PR, this PR establishes a hybrid automation architecture rolling out in manageable weekly batches:Renovate Lockfile Maintenance (
.github/renovate.json):bundle lock --updateruns (before 5am on monday).chore(deps): maintain Gemfile.lock files) in compliance with Ruby Cloud SDK team versioning rules.google-cloud-coregoogle-cloud-storagegoogle-cloud-pubsubgoogle-cloud-spannergoogle-cloud-bigquerygoogle-cloud-errorsBatch Generation Workflow (
.github/workflows/generate-lockfiles.yml):Gemfile.lockfiles in parallel batches without exceeding hosted runner container timeout limits.Rollout Cadence
google-cloud-[a-d]*)google-cloud-[e-o]*)google-cloud-[p-z]*)Reviewed and coordinated with @andreassa as part of the multi-phase compliance rollout.