Repository navigation
chore(core): upgrade @google/genai to 3.3 - #597
Merged
Merged
Conversation
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
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.
Dependabot's #592, and now #621 for 3.3, can't go in as they are. Their update job only changes
packages/core/package.json, so the lockfile keeps 2.30.0 and CI stops at install. This does the upgrade by hand, to 3.3.What 3.0 changes for us:
v1betatov1, and the-latestmodel aliases (gemini-flash-latestand the others) don't exist onv1.GeminiProvidernow passesapiVersion: 'v1beta'(packages/core/src/providers/gemini.ts:183), so requests go to the same endpoint as on 2.x. Moving tov1can be its own change after a live check.>=22, so nothing changes for users.CodeExecutionResultStep.resultchanged type, but that's in the Interactions API, which core doesn't use.3.1 to 3.3 only add features. The range is
^3.3.0and the lockfile has 3.3.0. 3.4 and 3.5 (out today) add features too, mostly to the Interactions API.How I tested this
tests/providers/custom-fetch.test.tsnow checks that the request goes to/v1beta/models/...:streamGenerateContent. With 3.2 and noapiVersionit failed, since the URL was/v1/models/gemini-3.5-flash-lite:streamGenerateContent.gemini-step.test.tsreplays the recorded Gemini responses and checks each request body against the recorded one, so 3.3 sends the same requests 2.30 did.pnpm -r build,pnpm -r typecheck,pnpm test(2562 passed),pnpm lint(no errors) andpnpm api:check.The live check against Gemini (a plain reply, a tool call with its thought signature, and usage) is part of the provider smoke test before the next release.