fix(google): fix serviceTier to be correctly formatted for Vertex API#14393
Merged
felixarntz merged 5 commits intomainfrom Apr 13, 2026
Merged
fix(google): fix serviceTier to be correctly formatted for Vertex API#14393felixarntz merged 5 commits intomainfrom
serviceTier to be correctly formatted for Vertex API#14393felixarntz merged 5 commits intomainfrom
Conversation
lgrammel
approved these changes
Apr 13, 2026
vercel-ai-sdk bot
pushed a commit
that referenced
this pull request
Apr 13, 2026
…PI (#14393) ## Background Follow up to #13915 and #14090: Turns out the Vertex API did _not_ apply the same change the Gemini API did, which originally prompted the #14090 follow-up. The Vertex API does not support the values `standard`, `flex`, and `priority` - instead it expects `SERVICE_TIER_{UPPERCASE_VALUE}`. ## Summary Sanitizes the input value accordingly if the Google provider implementation is used with Vertex. ## Manual Verification Run the new examples to verify. ## Checklist <!-- Do not edit this list. Leave items unchecked that don't apply. If you need to track subtasks, create a new "## Tasks" section Please check if the PR fulfills the following requirements: --> - [x] Tests have been added / updated (for bug fixes / features) - [ ] Documentation has been added / updated (for bug fixes / features) - [x] A _patch_ changeset for relevant packages has been added (for bug fixes / features - run `pnpm changeset` in the project root) - [x] I have reviewed this pull request (self-review)
Contributor
|
✅ Backport PR created: #14397 |
vercel-ai-sdk bot
added a commit
that referenced
this pull request
Apr 13, 2026
…r Vertex API (#14397) This is an automated backport of #14393 to the release-v6.0 branch. FYI @felixarntz Co-authored-by: Felix Arntz <felix.arntz@vercel.com>
Contributor
|
🚀 Published in:
|
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
2 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.
Background
Follow up to #13915 and #14090: Turns out the Vertex API did not apply the same change the Gemini API did, which originally prompted the #14090 follow-up.
The Vertex API does not support the values
standard,flex, andpriority- instead it expectsSERVICE_TIER_{UPPERCASE_VALUE}.Summary
Sanitizes the input value accordingly if the Google provider implementation is used with Vertex.
Manual Verification
Run the new examples to verify.
Checklist
pnpm changesetin the project root)