chore: update googleapis commitish to f3ff3a1 - #13989
Open
cloud-java-bot wants to merge 2 commits into
Open
Conversation
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the library version for multiple Google Cloud Java client libraries (e.g., accessapproval, accesscontextmanager, admanager, etc.) to their latest versions and updates the corresponding documentation links in the README files. Additionally, it adds the SearchMessages method to the ChatServiceClient and updates the Address and Commitment protobuf definitions with new purpose and type values. I have no feedback to provide as these changes appear to be standard library maintenance and feature additions.
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.
Updated googleapis commitish in librarian.yaml to googleapis/googleapis@f3ff3a1
💡 Note: If this PR is still open when the daily update workflow runs next, it will be closed and replaced with a new PR containing the latest updates.