Bump api-go to 1.32.0 to include Versioning 2 API changes #1439
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
ShahabT
commented
Apr 10, 2024
ShahabT
changed the title
Quinn-With-Two-Ns
approved these changes
Apr 10, 2024
cretz
approved these changes
Apr 10, 2024
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.
What was changed
Updating api-go version to include proto field renames related for Versioning 2.
Why?
Server depends on sdk-go, before merging versioning-2 branch into server's main we need to have a SDK version that compiles with the latest proto.
Checklist
Replaced occurrences of UseCompatibleVersion with its new name based on proto changes. These names are not exposed to the user.
Closes
How was this tested:
No behavior change.
No need.