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

Patch Changes

• d29f41e: Fix README typography and spacing

[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 facilitates a new release for the @googleworkspace/cli package, incrementing its version to 0.1.5. This update integrates a recent fix for README typography and spacing, ensuring that all package metadata and changelogs reflect the new version and its associated changes. The PR was automatically generated by the Changesets release GitHub action, preparing the package for publication.

Highlights

• Version Bump: The @googleworkspace/cli package has been updated to version 0.1.5 across all relevant configuration files.
• README Fix: A patch change addressing README typography and spacing has been incorporated into this release.

Changelog

• .changeset/fix-readme-typography.md
  • Removed the changeset file after its content was applied to the release.
• CHANGELOG.md
  • Added a new entry for version 0.1.5 under @googleworkspace/cli.
  • Included the patch change description "Fix README typography and spacing".
• Cargo.lock
  • Updated the gws package version from 0.1.4 to 0.1.5.
• Cargo.toml
  • Updated the gws package version from 0.1.4 to 0.1.5.
• package.json
  • Updated the @googleworkspace/cli package version from 0.1.4 to 0.1.5.

Activity

• This pull request was automatically opened by the googleworkspace-bot via the Changesets release GitHub action.
• The PR is designed to be merged when a release is ready, triggering automatic package publication to npm.

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 handles the version bump to 0.1.5 for the @googleworkspace/cli package. The changes, generated by the Changesets release action, include updating the version in package.json, Cargo.toml, and Cargo.lock, as well as updating CHANGELOG.md. These changes are consistent and correct for an automated release. No issues were found during the review.