fix: pin devDependencies to exact versions in package.json

[xiaolai]

Automated audit: This PR was generated by NLPM, a natural language programming linter, running via claude-code-action. Please evaluate the diff on its merits.

package.json uses caret ranges (^) for both @changesets/cli and lefthook in devDependencies. Caret ranges allow any compatible minor or patch version to be installed without an explicit update commit. This means:

1. A pnpm install in a fresh environment (e.g., a new developer machine or a CI ephemeral runner without a cache) can silently pull in a newer version than the one tested.
2. Supply-chain updates — including potentially malicious patch releases — could reach developer environments and CI without a code review.

Pinning to exact versions (2.29.8 and 2.1.2) ensures that every dependency upgrade is a deliberate, reviewable change. The existing pnpm-lock.yaml already records exact resolved versions; this change makes package.json consistent with that intent.

[changeset-bot]

🦋 Changeset detected

Latest commit: 71f64a6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@googleworkspace/cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[gemini-code-assist]

Summary of Changes

Hello, 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 improves supply-chain security and build reproducibility by pinning development dependencies to exact versions. By removing caret ranges, the project ensures that environments remain consistent and that all dependency updates are intentional and subject to code review.

Highlights

• Dependency Pinning: Updated devDependencies in package.json to use exact versions instead of caret ranges for @changesets/cli and lefthook.
• Changeset Added: Included a new changeset file to document the change in dependency management policy.

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.

Footnotes

1. Review the Generative AI Prohibited Use Policy, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request pins the development dependencies @changesets/cli and lefthook to exact versions in package.json to ensure consistent environments and prevent unreviewed updates. A changeset file has been added to document this change. I have no feedback to provide.