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 @googleworkspace/cli version 0.9.1 through the Changesets GitHub action. The release incorporates a significant patch that improves security by migrating encryption key storage from a local file to the OS keyring when available, and subsequently removing the old file.

Highlights

• Version Release: The @googleworkspace/cli package has been released as version 0.9.1.
• Security Improvement: The CLI now stops persisting encryption keys to a file (.encryption_key) 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, enhancing security.

Changelog

• CHANGELOG.md
  • Added new patch release 0.9.1 entry.
  • Included details about the encryption key persistence fix.
• Cargo.lock
  • Updated gws package version to 0.9.1.
• Cargo.toml
  • Updated gws package version to 0.9.1.
• package.json
  • Updated @googleworkspace/cli package version to 0.9.1.

Activity

• Pull request automatically opened by googleworkspace-bot via the Changesets release GitHub action to prepare for a new version 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 contains automated version bumps for the v0.9.1 release. The changes correctly update versions across package.json, Cargo.toml, and lockfiles, and updates CHANGELOG.md accordingly. While the changes in this PR are correct, a review of the related codebase reveals a critical performance and stability issue. Several async functions perform blocking I/O operations (like file access and keyring operations) on the async runtime thread. This can lead to severe performance degradation or deadlocks. For instance, functions in src/token_storage.rs and src/auth.rs call synchronous, blocking functions from src/credential_store.rs. It is strongly recommended to wrap these blocking calls in tokio::task::spawn_blocking in a follow-up PR to prevent blocking the async executor.

[codecov]

Codecov Report

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

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #348   +/-   ##
=======================================
  Coverage   61.72%   61.72%           
=======================================
  Files          38       38           
  Lines       14603    14603           
=======================================
  Hits         9014     9014           
  Misses       5589     5589           

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