fix(patch): cherry-pick e1bd1d2 to release/v0.27.0-preview.6-pr-18209 to patch version v0.27.0-preview.6 and create version 0.27.0-preview.7

[gemini-cli-robot]

This PR automatically cherry-picks commit e1bd1d2 to patch version v0.27.0-preview.6 in the preview release to create version 0.27.0-preview.7.

[gemini-code-assist]

Summary of Changes

Hello @gemini-cli-robot, I'm Gemini Code Assist¹! 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 is an automated cherry-pick to patch a preview release, specifically updating the retry mechanism within the core package. The primary goal is to centralize and standardize the default maximum number of retry attempts by introducing a dedicated constant, thereby improving maintainability and consistency in how retry logic is configured and reported.

Highlights

• Standardized Default Retry Attempts: Introduced a new constant, DEFAULT_MAX_ATTEMPTS, set to 3, to standardize the default number of retry attempts across the retry utility and its consumers.
• Centralized Retry Configuration: The GeminiChat class now uses the DEFAULT_MAX_ATTEMPTS constant when emitting retry attempt events, ensuring consistency with the core retry utility's default settings.

Changelog

• packages/core/src/core/geminiChat.ts
  • Imported the new DEFAULT_MAX_ATTEMPTS constant from the retry utility.
  • Updated the maxAttempts property in the emitRetryAttempt event to use DEFAULT_MAX_ATTEMPTS as the fallback value, replacing the hardcoded 10.
• packages/core/src/utils/retry.ts
  • Exported a new constant DEFAULT_MAX_ATTEMPTS with a value of 3.
  • Modified DEFAULT_RETRY_OPTIONS to use the DEFAULT_MAX_ATTEMPTS constant for its maxAttempts property, replacing the hardcoded 3.

Activity

• This pull request was automatically created by gemini-cli-robot to cherry-pick a specific commit (e1bd1d2) for a patch release (v0.27.0-preview.7).

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. ↩

[gemini-code-assist]

Code Review

This pull request cherry-picks a fix that corrects the reported number of maximum retry attempts. The changes introduce a DEFAULT_MAX_ATTEMPTS constant in retry.ts and use it in geminiChat.ts to ensure the onRetry event reports the correct value, which was previously hardcoded to an incorrect number. This change improves consistency and correctly reflects the retry behavior to the user. The implementation is correct and I have no further suggestions.

[github-actions]

Size Change: +142 B (0%)

Total Size: 23.5 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	23.5 MB	+142 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}