Workaround bug in google-claude-aiplatform evaluation extra (Python 3… - #71273
Merged
Conversation
boring-cyborg
Bot
added
area:providers
provider:google
potiuk
added
the
all versions
Member
Author
|
Reopened for 3.14 version |
vatsrahul1001
approved these changes
Aug 7, 2026
1 task
potiuk
added
the
full tests needed
potiuk
force-pushed
the
workaround-evaluation-extra-limits
branch
from
August 7, 2026 10:01
a91baa5 to
ec9955a
Compare
amoghrajesh
approved these changes
Aug 7, 2026
….15) The "evaluation" extra of google-cloud-aiplatform limits litellm to range that has security vulnerabilities when we want to get 3.14 support. Until this is fixed we need to bump litellm to higher version and remove the "evaluation" extra from google-cloud-aiplatform. Tracked in: googleapis/python-aiplatform#7057
potiuk
force-pushed
the
workaround-evaluation-extra-limits
branch
from
August 7, 2026 15:10
ec9955a to
613b169
Compare
This was referenced Aug 7, 2026
Vamsi-klu
added a commit
to Vamsi-klu/airflow
that referenced
this pull request
Aug 11, 2026
Reworks the optional Vertex AI evaluation change on top of apache#71273 (2c9d91e), which had removed the google-cloud-aiplatform[evaluation] extra from the base deps and inlined the evaluation requirements directly instead, as a workaround for the litellm security range tracked in googleapis/python-aiplatform#7057. Rather than reverting that, the inlined block -- including the litellm python_version markers and the tracking comment -- moves verbatim into a new "evaluation" entry under [project.optional-dependencies], so base installs stop pulling litellm and scikit-learn while the 3.14 security pin is preserved for anyone installing the extra. providers/google/README.rst and docs/index.rst tables are regenerated to match, and uv.lock is regenerated with the pinned uv 0.11.29 (uv lock --check passes; note main's lock was already stale, so the diff also picks up a few unrelated requires-dist specifiers).
1 task
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
3 participants
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.
….15)
The "evaluation" extra of google-cloud-aiplatform limits litellm to range that has security vulnerabilities when we want to get 3.14 support. Until this is fixed we need to bump litellm to higher version and remove the "evaluation" extra from google-cloud-aiplatform.
Tracked in: googleapis/python-aiplatform#7057
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.