Loosen constraints for google-api-core and google-cloud-aiplatform in TFX 1.13 #6384
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
|
Hi @lego0901 Can you please review this PR ? Thank you! |
|
Hi @lego0901 Can you please review this PR ? Thank you! |
|
Closed. |
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.
TFX 1.13 has constraints to google-api-core and google-cloud-aiplatform because of the protobuf versions, but TF 2.12 can accept protobuf>=3.20.3, so we can loosen those constraints in TFX 1.13 to allow for newer versions of these packages, which may use newer versions of protobuf.
So this change will allow TFX 1.13 to work with a wider range of versions of google-api-core and google-cloud-aiplatform. I followed the version constraints in r1.14.0 branch.
Fix #6375