Skip to content

chore(deps): update dependency google-cloud-aiplatform to v2 - #439

Open
twishabansal wants to merge 3 commits into
mainfrom
chore/aiplatform-v2-langchain-classic
Open

twishabansal wants to merge 3 commits into
mainfrom
chore/aiplatform-v2-langchain-classic

Conversation

@twishabansal

@twishabansal twishabansal commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Description

Supersedes #438 (cross-repo, so it couldn't be used as a base or pushed to). Carries renovate's bump plus the fix it needs.

aiplatform v2's langchain extra moves langchain 0.31.x, which relocated the legacy agent/chain APIs into langchain-classic. Two Vertex sample templates still import from the old paths.

  • Repoint hub, AgentExecutor, create_react_agent, create_retriever_tool and the two chains imports at langchain_classic. Behavior unchanged.
  • Bump samples/langchain_on_vertexai/requirements.txt in lockstep — it's what ReasoningEngine.create() installs, so on v1 the deployed agent wouldn't find langchain_classic.
  • Pin langchain-classic explicitly rather than relying on the extra.

Issue Reference

Supersedes #438

renovate-bot and others added 2 commits September 1, 2026 22:04
…tform v2

aiplatform v2's langchain extra moves langchain from 0.3 to 1.x, which
relocates the legacy agent and chain APIs into the separate
langchain-classic distribution that the extra now installs. Repoint the
two Vertex sample templates at their new locations.

Bump samples/langchain_on_vertexai/requirements.txt in lockstep. That
file is passed to ReasoningEngine.create() and is what the deployed
agent installs, so leaving it on v1 would resolve langchain 0.3 and fail
to find langchain_classic at import time.

Pin langchain-classic explicitly rather than relying on the extra to
supply it. The extra's contents are exactly what shifted here -- v2 also
dropped langchain-google-vertexai in favor of langchain-google-genai.
@twishabansal
twishabansal requested review from a team as code owners September 11, 2026 07:41
@product-auto-label product-auto-label Bot added the api: cloudsql-postgres Issues related to the googleapis/langchain-google-cloud-sql-pg-python API. label Sep 11, 2026
@dishaprakash

Copy link
Copy Markdown
Contributor

LGTM! Please check failing lint

gemini-2.0-flash-001 is retired, so the reasoning-engine integration test
fails at query time with a 404 on the publisher model. Verified
gemini-2.5-flash resolves in langchain-cloud-sql-testing/us-central1.

No token caps in these templates, so 2.5 thinking has no budget to starve.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: cloudsql-postgres Issues related to the googleapis/langchain-google-cloud-sql-pg-python API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants