chore(deps): sync fork with upstream v0.40.0#5
Merged
ik-gemini-bot merged 171 commits intomainfrom May 3, 2026
Merged
Conversation
…hs (google-gemini#24763) Co-authored-by: Spencer <spencertang@google.com>
Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> Co-authored-by: g-samroberts <samroberts@google.com>
Co-authored-by: Coco Sheng <cocosheng@google.com>
Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> Co-authored-by: Sam Roberts <158088236+g-samroberts@users.noreply.github.com>
…nd queuing of named suites (google-gemini#24941)
…kpointing error (google-gemini#19775) Co-authored-by: David Pierce <davidapierce@google.com>
…without changes (google-gemini#24773) Co-authored-by: Coco Sheng <cocosheng@google.com>
…y editing across four tiers (google-gemini#25716)
…d '1.0.0' (google-gemini#24414) Co-authored-by: cynthialong0-0 <82900738+cynthialong0-0@users.noreply.github.com>
…23895) Co-authored-by: cynthialong0-0 <82900738+cynthialong0-0@users.noreply.github.com>
Co-authored-by: David Pierce <davidapierce@google.com>
…s mode (google-gemini#25814) Co-authored-by: galz10 <galzahavi@google.com> Co-authored-by: davidapierce <davidapierce@google.com>
…list (google-gemini#25720) Co-authored-by: David Pierce <davidapierce@google.com> Co-authored-by: Keith Schaab <keithsc@google.com> Co-authored-by: Keith Schaab <keith.schaab@gmail.com> Co-authored-by: Emily Hedlund <ehedlund@google.com>
… to patch version v0.40.0-preview.3 and create version 0.40.0-preview.4 (google-gemini#25942) Co-authored-by: Tommaso Sciortino <sciortino@gmail.com>
… [CONFLICTS] (google-gemini#26124) Co-authored-by: David Pierce <davidapierce@google.com>
Align the branch history with fork main by merging upstream v0.40.0, resolving conflicts toward upstream where broad churn occurred, and keeping fork versioning plus fallback test compatibility.
This cleans the repository after the upstream merge and ignores the helper file so future local commits do not pollute branch diffs.
ik-gemini-bot
force-pushed
the
spigell/chore/update-to-0.40.0
branch
from
24e2eee to
02604c6
Compare
Document the final workflow trigger step for cases where a new container image is required, including the exact workflow name and inputs, and warn against passing the branch name as the version.
Document that the fork should be bumped from upstream without applying fork patches back onto the upstream release branch, keeping fork-specific changes isolated to the fork resync workflow.
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
20 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.
Summary
Updates the fork to upstream release v0.40.0, carrying forward custom patches and resolving test incompatibilities introduced by new model availability and fallback logic in the 0.40.0 update.
Details
This PR aligns the fallback tests and dynamic model routing expectations with the newly introduced model policy semantics in 0.40.0:
pro/flash) lookups.Related Issues
None
How to Validate
npm run buildnpm run test(ensurepackages/core/src/fallback/handler.test.tspasses).Pre-Merge Checklist