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

Patch Changes

• a0ad089: Speed up CI builds with Swatinem/rust-cache, sccache, and build artifact reuse for smoketests
• 30d929b: Optimize demo GIF and improve README

[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 automates the release process for the @googleworkspace/cli package, incrementing its version to 0.1.1. It incorporates recent changes, including CI build optimizations and documentation enhancements, into the project's changelog and updates the package metadata accordingly. This PR is generated by the Changesets action and is ready to be merged to publish the new package version.

Highlights

• CI Build Speed: CI builds were sped up by integrating Swatinem/rust-cache, sccache, and reusing build artifacts for smoketests.
• Documentation Improvements: The demo GIF was optimized and the README file was improved.

Changelog

• .changeset/ci-build-speed.md
  • Removed the changeset file after its content was incorporated into the changelog.
• .changeset/optimize-demo-gif.md
  • Removed the changeset file after its content was incorporated into the changelog.
• CHANGELOG.md
  • Added a new changelog entry for version 0.1.1, detailing CI build speed improvements and README/demo GIF optimizations.
• package.json
  • Updated the package version from 0.1.0 to 0.1.1.

Activity

• The pull request was automatically opened by the googleworkspace-bot using the Changesets release GitHub action to prepare for a new package 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 appears to be an automated release preparation managed by the Changesets action. It correctly bumps the package version to 0.1.1, updates the CHANGELOG.md with the recent patch changes, and removes the corresponding changeset files. These changes are standard for this type of release workflow and look correct. There are no code issues to address.