fix: onboarding libraries to Librarian / location mixin workarounds - #36484
Merged
Conversation
suztomo
marked this pull request as ready for review
August 31, 2026 15:54
aandreassa
approved these changes
Aug 31, 2026
This was referenced Sep 1, 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.
Summary
This PR onboards 14 gems to Librarian that previously contained
.owlbot.rbworkarounds for spuriousGoogle::Cloud::Locationlinks (gapic-generator-ruby#824).See tracking issue: googleapis/librarian#7444
Background & Analysis
Historically,
gapic-generator-rubyconverted markdown references toGoogle::Cloud::Locationinto invalid YARD cross-reference links ({::Google::Cloud::Location::Location ...}), which failed doc builds because the class is in an external gem dependency (google-cloud-location).These gems maintained
.owlbot.rbscripts withcontent.gsubto work around the bug.With the upstream generator bug fix in gapic-generator-ruby#1211 (included in
gapic-generator-cloud >= 0.51.0), the generator no longer emits invalid YARD links for cross-package mixin objects. As a result, the.owlbot.rbworkarounds are obsolete and all 14 libraries can be safely onboarded to Librarian.Onboarded Gems (14)
google-cloud-discovery_engine-v1google-cloud-edge_container-v1google-cloud-firestore-admin-v1google-cloud-kms-v1google-cloud-memcache-v1google-cloud-memcache-v1beta2google-cloud-netapp-v1google-cloud-oracle_database-v1google-cloud-scheduler-v1google-cloud-scheduler-v1beta1google-cloud-tasks-v2google-cloud-tasks-v2beta2google-cloud-tasks-v2beta3google-cloud-vmware_engine-v1Diff Analysis
.OwlBot.yaml,.owlbot.rb, and.owlbot-manifest.jsonfrom all 14 gem directories.755to644.proto_docs: Removed unreferencedproto_docs/google/type/expr.rbingoogle-cloud-kms-v1andgoogle-cloud-vmware_engine-v1.Local Verification
Ran full CI suite across all 14 gems:
Result: All tests passed, 0 failures, 0 errors, 0 rubocop offenses.