Force google guava to 32.0.1 #536
Merged
Conversation
This file contains 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
Signed-off-by: Ashish Agrawal <[email protected]>
lezzago
requested review from
amsiglan,
AWSHurneyt,
getsaurabh02,
praveensameneni,
sbcd90 and
eirsep
as code owners
getsaurabh02
approved these changes
Sep 6, 2023
amsiglan
approved these changes
Sep 6, 2023
opensearch-trigger-bot bot
pushed a commit
that referenced
this pull request
Sep 6, 2023
Signed-off-by: Ashish Agrawal <[email protected]> (cherry picked from commit 5178cc0)
sbcd90
pushed a commit
that referenced
this pull request
Sep 6, 2023
Signed-off-by: Ashish Agrawal <[email protected]>
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.
Description
Force google guava to 32.0.1 due to spotless still using 31.1
Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.