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

Patch Changes

• 06aa698: fix(auth): dynamically fetch scopes from Discovery docs when -s specifies services not in static scope lists
• 06aa698: fix(auth): format extract_scopes_from_doc and deduplicate dynamic scopes
• 5e7d120: Bring +forward behavior in line with Gmail's web UI: keep the forward in the sender's original thread, add a blank line between the forwarded message metadata and body, and remove the spurious closing delimiter.
• 2782cf1: Fix gmail +triage 403 error by using gmail.readonly scope instead of gmail.modify to avoid conflict with gmail.metadata scope that does not support the q parameter

[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, bumping its version to 0.9.2. The primary driver for this release is a critical bug fix addressing a 403 error encountered when using the gmail +triage functionality, which involved a scope adjustment. This release process is automated by the Changesets GitHub action.

Highlights

• Gmail +triage 403 error fix: Resolved a 403 error occurring with gmail +triage by adjusting the required scope from gmail.modify to gmail.readonly. This change prevents conflicts with the gmail.metadata scope, which does not support the q parameter.
• Version Bump: The @googleworkspace/cli package has been updated to version 0.9.2 across package.json, Cargo.toml, and Cargo.lock.

Changelog

• .changeset/fix-gmail-triage-scope.md
  • Removed the temporary changeset file after its content was incorporated into the main changelog.
• CHANGELOG.md
  • Added a new entry for version 0.9.2, detailing the fix for the gmail +triage 403 error.
  • Included the specific patch change ID 2782cf1.
• Cargo.lock
  • Updated the gws package version to 0.9.2.
• Cargo.toml
  • Updated the gws package version to 0.9.2.
• package.json
  • Updated the @googleworkspace/cli package version to 0.9.2.

Activity

• This pull request was automatically opened by the Changesets release GitHub action.
• The PR description provides instructions for merging to publish packages to npm or for updating the PR with new changesets.

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 release of version 0.9.2. The changes include updating the version number in package.json, Cargo.toml, and Cargo.lock, as well as adding the release notes to CHANGELOG.md. The changes are consistent with an automated release process and appear correct. This PR is ready for merging to trigger the publishing of the new version.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.72%. Comparing base (2782cf1) to head (64b048e).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #351      +/-   ##
==========================================
- Coverage   61.74%   61.72%   -0.02%     
==========================================
  Files          38       38              
  Lines       14603    14603              
==========================================
- Hits         9016     9014       -2     
- Misses       5587     5589       +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.

[github-actions]

/gemini review

[github-actions]

/gemini review