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

Patch Changes

• 5872dbe: Stop persisting encryption key to .encryption_key file when OS keyring is available. Existing file-based keys are migrated into the keyring and the file is removed on next CLI invocation.

[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 of the @googleworkspace/cli package to version 0.9.1. The core functional change included in this release enhances encryption key management by transitioning from file-based storage to OS keyring integration, improving security and user experience. The PR updates various project configuration files to reflect this new version.

Highlights

• Encryption Key Management: The CLI now stops persisting encryption keys to a .encryption_key file when an OS keyring is available. Existing file-based keys are migrated into the keyring, and the file is removed on the next CLI invocation.

Changelog

• CHANGELOG.md
  • Added release notes for version 0.9.1, detailing the change in encryption key persistence.
• Cargo.lock
  • Updated the gws package version from 0.9.0 to 0.9.1.
• Cargo.toml
  • Updated the gws package version from 0.9.0 to 0.9.1.
• flake.lock
  • Updated the nixpkgs dependency lock hash and lastModified timestamp.
• package.json
  • Updated the @googleworkspace/cli package version from 0.9.0 to 0.9.1.

Activity

• The pull request was automatically opened by the Changesets release GitHub action to facilitate 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 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. ↩

[gemini-code-assist]

Code Review

This pull request, generated by the Changesets release action, prepares for the v0.9.1 release. The modifications are confined to version number increments across CHANGELOG.md, Cargo.toml, Cargo.lock, and package.json, and an update to flake.lock. The changelog entry for this version describes a change to stop persisting encryption keys to a file when an OS keyring is available, migrating existing keys. As the provided diffs only contain metadata and versioning changes, there are no code logic changes to review. No issues were found within the scope of the modified files.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.74%. Comparing base (5872dbe) to head (917c58b).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #350      +/-   ##
==========================================
+ Coverage   61.72%   61.74%   +0.01%     
==========================================
  Files          38       38              
  Lines       14603    14603              
==========================================
+ Hits         9014     9016       +2     
+ Misses       5589     5587       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.