chore/release: bump version to 0.21.0-nightly.20251213.977248e09

[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 is an automated maintenance task to update the version numbers for the nightly release of the @google/gemini-cli project. It ensures that all components, including the main CLI and its sub-packages, are synchronized to the latest development snapshot. This update also includes minor adjustments to dependency metadata in the lock file.

Highlights

• Automated Version Bump: The pull request performs an automated update of the project's version to 0.21.0-nightly.20251213.977248e09 across the main package and all associated sub-packages.
• Dependency Metadata Adjustments: Various peer dependency flags were adjusted within package-lock.json, with some being removed and others added, indicating a refinement in how these dependencies are declared or resolved.
• License Information Added: License information (Apache-2.0) has been explicitly added to the packages/cli and packages/core entries within the package-lock.json file.

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 for a nightly release, consistently updating package.json files and package-lock.json. However, a security audit identified multiple command injection vulnerabilities in the provided build scripts. These stem from the use of execSync with unsanitized external input, including command-line arguments, environment variables, and parsed file contents, with the most severe allowing arbitrary code execution via an environment variable. It is strongly recommended to remediate these issues by either validating all inputs against a strict allow-list or by using the safer execFile function.