Skip to content

fix(patch): cherry-pick 643f2c0 to release/v0.11.1-pr-12300 to patch version v0.11.1 and create version 0.11.2#12335

Merged
mattKorwel merged 1 commit intorelease/v0.11.1-pr-12300from
hotfix/v0.11.1/0.11.2/stable/cherry-pick-643f2c0/pr-12300
Oct 31, 2025
Merged

fix(patch): cherry-pick 643f2c0 to release/v0.11.1-pr-12300 to patch version v0.11.1 and create version 0.11.2#12335
mattKorwel merged 1 commit intorelease/v0.11.1-pr-12300from
hotfix/v0.11.1/0.11.2/stable/cherry-pick-643f2c0/pr-12300

Conversation

@gemini-cli-robot
Copy link
Copy Markdown
Collaborator

This PR automatically cherry-picks commit 643f2c0 to patch version v0.11.1 in the stable release to create version 0.11.2.

@github-actions github-actions Bot mentioned this pull request Oct 31, 2025
18 tasks
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @gemini-cli-robot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request applies a targeted patch to correct an issue where the model router was inadvertently disabled by default when using LOGIN_WITH_GOOGLE authentication. By adjusting the configuration and updating a relevant test, this change ensures consistent and expected behavior for the model router across different authentication methods. This fix is being cherry-picked to create a new patch version for a stable release.

Highlights

  • Model Router Configuration Update: The default configuration for disableModelRouterForAuth has been modified to no longer include AuthType.LOGIN_WITH_GOOGLE, meaning the model router will remain enabled by default for this authentication type.
  • Test Case Correction: A corresponding test case in config.test.ts was updated to assert that the model router remains enabled after LOGIN_WITH_GOOGLE authentication, reflecting the intended behavior change.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@mattKorwel mattKorwel merged commit f36dec6 into release/v0.11.1-pr-12300 Oct 31, 2025
8 of 11 checks passed
@mattKorwel mattKorwel deleted the hotfix/v0.11.1/0.11.2/stable/cherry-pick-643f2c0/pr-12300 branch October 31, 2025 02:20
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request is a cherry-pick to apply a fix that enables the model router by default for Google login. The change to the default configuration in packages/core/src/config/config.ts is correct. The corresponding test update in packages/core/src/config/config.test.ts is also correct in its logic, but it introduces an inconsistency between the test's description and its implementation, which could be misleading.

});
await config.refreshAuth(AuthType.LOGIN_WITH_GOOGLE);
expect(config.getUseModelRouter()).toBe(false);
expect(config.getUseModelRouter()).toBe(true);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The test's expectation on this line has been changed to assert that the model router is enabled (true). However, the test's description on line 578 (should disable model router by default for oauth-personal) is now inconsistent with this expectation. To avoid confusion, please update the test description to reflect the new expected behavior, for example: should enable model router by default for oauth-personal.

@github-actions
Copy link
Copy Markdown

Size Change: -2 B (0%)

Total Size: 20.1 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 20.1 MB -2 B (0%)
./bundle/sandbox-macos-permissive-closed.sb 1.03 kB 0 B
./bundle/sandbox-macos-permissive-open.sb 890 B 0 B
./bundle/sandbox-macos-permissive-proxied.sb 1.31 kB 0 B
./bundle/sandbox-macos-restrictive-closed.sb 3.29 kB 0 B
./bundle/sandbox-macos-restrictive-open.sb 3.36 kB 0 B
./bundle/sandbox-macos-restrictive-proxied.sb 3.56 kB 0 B

compressed-size-action

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.

4 participants