chore: release versions

[googleworkspace-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@googleworkspace/cli@0.1.2

Patch Changes

• 3cd4d52: Fix release pipeline to sync Cargo.toml version with changesets and create git tags for private packages

[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 is an automated release PR generated by the Changesets GitHub action. It updates the version of the @googleworkspace/cli package to 0.1.2 and includes a critical fix for the release pipeline, ensuring proper version synchronization and git tag creation for private packages.

Highlights

• Version Bump: The @googleworkspace/cli package has been updated from 0.1.1 to 0.1.2 across relevant configuration files.
• Release Pipeline Fix: This release incorporates a fix to synchronize Cargo.toml versions with Changesets and enable git tag creation for private packages, addressing a previous issue in the release pipeline.

Changelog

• CHANGELOG.md
  • Added a new version 0.1.2 entry with details about the release pipeline fix.
• Cargo.lock
  • Updated the gws package version from 0.1.1 to 0.1.2.
• Cargo.toml
  • Updated the gws package version from 0.1.1 to 0.1.2.
• package.json
  • Updated the @googleworkspace/cli package version from 0.1.1 to 0.1.2.

Activity

• This pull request was automatically opened by googleworkspace-bot via the Changesets release GitHub action to propose a new release.

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, generated by the Changesets action, handles the version bump to 0.1.2. While the version updates in package.json, Cargo.toml, Cargo.lock, and CHANGELOG.md are consistent and correct for a release, a critical security vulnerability was identified. Specifically, in scripts/version-sync.sh, untrusted input from package.json is improperly handled during the update of Cargo.toml, leading to a potential TOML injection. This requires immediate attention and should be addressed by using environment variables to pass data to awk safely. Other parts of the scripts, including the git tagging logic, appear to be secure.