chore/release: bump version to 0.21.0-nightly.20251212.54de67536

[gemini-cli-robot]

Automated version bump for nightly release.

[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 performs an automated version bump for the Gemini CLI project, incrementing the version number for a nightly release across the main project and all its sub-packages. This ensures that all components, including the sandbox image URI, are aligned with the latest development build.

Highlights

• Version Bump: The primary version for the @google/gemini-cli project and all its associated sub-packages has been updated to 0.21.0-nightly.20251212.54de67536.
• Sandbox Image URI Update: The sandboxImageUri configuration in the main package.json and packages/cli/package.json files has been updated to reflect the new nightly version.

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

[github-actions]

Size Change: -2 B (0%)

Total Size: 21.6 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	21.6 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}

[gemini-code-assist]

Code Review

This pull request performs an automated version bump to "0.21.0-nightly.20251212.54de67536", with version updates appearing consistent across package.json files and package-lock.json. However, a critical command injection vulnerability was identified in the scripts/version.js file. This vulnerability stems from the script's failure to sanitize user-provided command-line arguments, which could lead to arbitrary code execution. Additionally, suggestions have been provided to enhance the robustness of the scripts/version.js automation for future releases, which do not block this PR.

[gemini-code-assist]

The version bump is correct. However, reviewing the scripts/version.js script that automates this process, I found two areas for improvement to make the release process more robust and maintainable:

1. Incomplete lockfile update: The script runs npm install --workspace packages/cli --workspace packages/core --package-lock-only. This only considers a subset of workspaces and could lead to an inconsistent package-lock.json in the future. It should probably be npm install --package-lock-only to cover all workspaces.
2. Hardcoded paths for sandboxImageUri: The script hardcodes the paths to package.json and packages/cli/package.json to update sandboxImageUri. This should be made dynamic to automatically handle new packages.