Skip to content

Changelog for v0.34.0-preview.2#22220

Merged
g-samroberts merged 1 commit intomainfrom
changelog-v0.34.0-preview.2
Mar 16, 2026
Merged

Changelog for v0.34.0-preview.2#22220
g-samroberts merged 1 commit intomainfrom
changelog-v0.34.0-preview.2

Conversation

@gemini-cli-robot
Copy link
Collaborator

This PR contains the auto-generated changelog for the v0.34.0-preview.2 release.

Please review and merge.

@gemini-cli-robot gemini-cli-robot requested review from a team as code owners March 12, 2026 21:10
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 provides an auto-generated update to the preview release changelog document. It increments the version number and includes a new fix entry, ensuring the documentation accurately reflects the latest preview release.

Highlights

  • Version Update: The preview release version in docs/changelogs/preview.md has been updated from v0.34.0-preview.1 to v0.34.0-preview.2.
  • New Fix Entry Added: A new fix entry for a cherry-picked patch (8432bce) has been added to the changelog, specifically for version v0.34.0-preview.2.
  • Changelog Link Updated: The 'Full Changelog' comparison link was updated to reflect the new v0.34.0-preview.2 version.
Changelog
  • docs/changelogs/preview.md
    • Updated the main release version heading from v0.34.0-preview.1 to v0.34.0-preview.2.
    • Added a new fix entry detailing a cherry-picked patch for v0.34.0-preview.2.
    • Modified the 'Full Changelog' comparison link to reference v0.34.0-preview.2.
Activity
  • The pull request was auto-generated by gemini-cli-robot to update the changelog for the v0.34.0-preview.2 release.
  • The author requested review and merge of the auto-generated content.
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.

Copy link
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 updates the preview changelog for version v0.34.0-preview.2. While the version numbers and links are correctly updated, I have raised one point of feedback regarding the clarity of the auto-generated changelog entry. The current entry describes the internal patching process rather than the user-facing change, which reduces the usefulness of the changelog. Improving the release automation to generate more descriptive entries is recommended.

Note: Security Review has been skipped due to the limited scope of the PR.

Comment on lines +31 to +34
- fix(patch): cherry-pick 8432bce to release/v0.34.0-preview.1-pr-22069 to patch
version v0.34.0-preview.1 and create version 0.34.0-preview.2 by
@gemini-cli-robot in
[#22205](https://github.com/google-gemini/gemini-cli/pull/22205)
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The auto-generated changelog entry is very technical and describes the internal patching process rather than the actual fix that users would be interested in. This makes it difficult for users to understand the value of the patch and whether it's relevant to them. For example, if this patch contained a critical security fix, this entry would not communicate that urgency, which could cause problems for users who don't install the update.

It is recommended to improve the release automation to generate more descriptive changelog entries. The automation should ideally use the commit message of the cherry-picked commit (8432bce in this case) as the basis for the changelog entry, rather than a generic description of the cherry-pick action.

A more user-friendly entry would look something like this:

- fix: [Description of the actual fix from commit 8432bce] ([#22205](https://github.com/google-gemini/gemini-cli/pull/22205))

While this change can be made manually for this PR, the underlying issue is in the automation scripts (e.g., scripts/releasing/create-patch-pr.js) and should be addressed there for future releases.

References
  1. For patch releases, the auto-generated changelog must only list the specific changes for that patch. This comment highlights that the current auto-generated entry describes the internal patching process rather than the specific, user-facing fix, making it less aligned with the rule's intent for clear and specific patch details.

@github-actions
Copy link

Size Change: -4 B (0%)

Total Size: 26 MB

Filename Size Change
./bundle/chunk-QRRBF6VR.js 0 B -3.62 MB (removed) 🏆
./bundle/chunk-YFRXPORX.js 0 B -13.3 MB (removed) 🏆
./bundle/core-3JO26QAA.js 0 B -40.3 kB (removed) 🏆
./bundle/devtoolsService-N4KERIOX.js 0 B -27.7 kB (removed) 🏆
./bundle/interactiveCli-MKJKGJZJ.js 0 B -1.59 MB (removed) 🏆
./bundle/oauth2-provider-SWDO55LC.js 0 B -9.19 kB (removed) 🏆
./bundle/chunk-3YY3HYX3.js 13.3 MB +13.3 MB (new file) 🆕
./bundle/chunk-RSVSM2BK.js 3.62 MB +3.62 MB (new file) 🆕
./bundle/core-D67DCMFW.js 40.3 kB +40.3 kB (new file) 🆕
./bundle/devtoolsService-WX3WV3TD.js 27.7 kB +27.7 kB (new file) 🆕
./bundle/interactiveCli-G2TKAG2I.js 1.59 MB +1.59 MB (new file) 🆕
./bundle/oauth2-provider-2HWVCX4T.js 9.19 kB +9.19 kB (new file) 🆕
ℹ️ View Unchanged
Filename Size Change
./bundle/chunk-34MYV7JD.js 2.45 kB 0 B
./bundle/chunk-37ZTTFQF.js 966 kB 0 B
./bundle/chunk-5AUYMPVF.js 858 B 0 B
./bundle/chunk-664ZODQF.js 124 kB 0 B
./bundle/chunk-DAHVX5MI.js 206 kB 0 B
./bundle/chunk-FXR7IA3Q.js 1.95 MB 0 B
./bundle/chunk-IUUIT4SU.js 56.5 kB 0 B
./bundle/chunk-RJTRUG2J.js 39.8 kB 0 B
./bundle/devtools-36NN55EP.js 696 kB 0 B
./bundle/dist-T73EYRDX.js 356 B 0 B
./bundle/gemini.js 689 kB 0 B
./bundle/getMachineId-bsd-TXG52NKR.js 1.55 kB 0 B
./bundle/getMachineId-darwin-7OE4DDZ6.js 1.55 kB 0 B
./bundle/getMachineId-linux-SHIFKOOX.js 1.34 kB 0 B
./bundle/getMachineId-unsupported-5U5DOEYY.js 1.06 kB 0 B
./bundle/getMachineId-win-6KLLGOI4.js 1.72 kB 0 B
./bundle/keychain-token-storage-A3WKTJK3.js 0 B -518 B (removed) 🏆
./bundle/memoryDiscovery-URXPIMBI.js 922 B 0 B
./bundle/multipart-parser-KPBZEGQU.js 11.7 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/client/main.js 221 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/_client-assets.js 227 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/index.js 11.5 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/types.js 132 B 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-open.sb 3.36 kB 0 B
./bundle/sandbox-macos-restrictive-proxied.sb 3.56 kB 0 B
./bundle/sandbox-macos-strict-open.sb 4.82 kB 0 B
./bundle/sandbox-macos-strict-proxied.sb 5.02 kB 0 B
./bundle/src-QVCVGIUX.js 47 kB 0 B
./bundle/tree-sitter-7U6MW5PS.js 274 kB 0 B
./bundle/tree-sitter-bash-34ZGLXVX.js 1.84 MB 0 B
./bundle/undici-4X2YZID5.js 360 B 0 B
./bundle/keychain-token-storage-73RTQXE3.js 518 B +518 B (new file) 🆕

compressed-size-action

@gemini-cli gemini-cli bot added the status/need-issue Pull requests that need to have an associated issue. label Mar 12, 2026
@g-samroberts g-samroberts added this pull request to the merge queue Mar 16, 2026
Merged via the queue into main with commit dfe22aa Mar 16, 2026
29 of 30 checks passed
@g-samroberts g-samroberts deleted the changelog-v0.34.0-preview.2 branch March 16, 2026 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status/need-issue Pull requests that need to have an associated issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants