Skip to content

chore(opencode): pin google providers before tool id regression#29423

Merged
rekram1-node merged 1 commit into
devfrom
fix/google-vertex-tool-id-regression
May 26, 2026
Merged

chore(opencode): pin google providers before tool id regression#29423
rekram1-node merged 1 commit into
devfrom
fix/google-vertex-tool-id-regression

Conversation

@rekram1-node
Copy link
Copy Markdown
Collaborator

Summary

  • set @ai-sdk/google to 3.0.73, retaining the no-argument tool-call thoughtSignature fix introduced in 3.0.71
  • set @ai-sdk/google-vertex to 4.0.128, which resolves @ai-sdk/google@3.0.73 instead of the 3.0.74+ serializer that emits unsupported tool-call IDs on Vertex v1 paths
  • remove the mixed state on dev, where direct Google was 3.0.63 but Vertex still pulled @ai-sdk/google@3.0.75

Regression

@ai-sdk/google@3.0.74+ serializes functionCall.id and functionResponse.id. Vertex v1 / Express-mode and the observed GCP-routed Gemini endpoint reject these fields with Unknown name "id", breaking tool continuations. This is an upstream serializer regression exposed by supported provider paths, not a user configuration error.

Validation

  • bun install --ignore-scripts
  • packages/core: bun typecheck && bun test "test/plugin/provider-google.test.ts" "test/plugin/provider-google-vertex.test.ts" (11 pass)
  • packages/opencode: bun typecheck && bun test "test/provider/transform.test.ts" (224 pass)
  • packages/llm: bun typecheck && bun test "test/provider/gemini.test.ts" (11 pass)

@rekram1-node rekram1-node merged commit 28dbd4a into dev May 26, 2026
13 checks passed
@rekram1-node rekram1-node deleted the fix/google-vertex-tool-id-regression branch May 26, 2026 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant