fix(patch): cherry-pick c43500c to release/v0.30.0-preview.1-pr-19502 to patch version v0.30.0-preview.1 and create version 0.30.0-preview.2

[gemini-cli-robot]

This PR automatically cherry-picks commit c43500c to patch version v0.30.0-preview.1 in the preview release to create version 0.30.0-preview.2.

[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 automates a critical patch for a preview release, specifically v0.30.0-preview.1, by integrating a commit that introduces the punycode library. The primary goal is to ensure the punycode dependency is correctly included and resolved within the build system, thereby addressing potential issues or enabling new functionality in the 0.30.0-preview.2 version.

Highlights

• Dependency Addition: The punycode package was added as a new direct dependency in package.json and package-lock.json.
• Build Configuration Update: Esbuild configurations were updated across esbuild.config.js and packages/vscode-ide-companion/esbuild.js to include aliases for the punycode module, ensuring proper resolution during the build process.
• Automated Patch Release: This pull request represents an automated cherry-pick of a specific commit (c43500c) to create a new patch version (v0.30.0-preview.2) for the preview release branch.

Changelog

• esbuild.config.js
  • Added a common alias for punycode to cliConfig and a2aServerConfig.
• package-lock.json
  • Included punycode as a new direct dependency.
  • Removed the devOptional flag for punycode.
• package.json
  • Added punycode as a new direct dependency.
• packages/vscode-ide-companion/esbuild.js
  • Added an alias for punycode in the esbuild configuration.

Activity

• Automated cherry-pick of commit c43500c50b3184802ac45135c8d0fd4cb665c9be to the release/v0.30.0-preview.1-pr-19502 branch.
• Creation of new preview version 0.30.0-preview.2 as a result of the patch.

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 for a build issue related to the punycode module. The changes involve adding punycode as a direct dependency and configuring the esbuild bundler to alias it correctly. This is a standard approach to resolve issues with the deprecated punycode core module in Node.js. The changes are applied consistently across the different build configurations in the project. The implementation is correct and I see no issues with this pull request.

[github-actions]

Size Change: +7.62 kB (+0.03%)

Total Size: 24.5 MB

Filename	Size	Change
./bundle/gemini.js	24.5 MB	+7.62 kB (+0.03%)

ℹ️ View Unchanged

Filename	Size
./bundle/sandbox-macos-permissive-open.sb	890 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB
./bundle/sandbox-macos-strict-open.sb	4.82 kB
./bundle/sandbox-macos-strict-proxied.sb	5.02 kB

_{compressed-size-action}