Skip to content

chore: release versions#606

Merged
jpoehnelt merged 2 commits intomainfrom
changeset-release/main
Mar 24, 2026
Merged

chore: release versions#606
jpoehnelt merged 2 commits intomainfrom
changeset-release/main

Conversation

@googleworkspace-bot
Copy link
Copy Markdown
Collaborator

@googleworkspace-bot googleworkspace-bot commented Mar 24, 2026

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

Patch Changes

  • b8fd3d9: fix(client): add 10s connect timeout to prevent hangs on initial connection
  • 2bfcca9: Move version from top-level SKILL.md frontmatter to metadata and track CLI version
  • 2ddb46e: test(gmail): add regression tests for RFC 2822 display name quoting
  • 75a7121: Sync generated skills with latest Google Discovery API specs

@googleworkspace-bot googleworkspace-bot added area: skills area: distribution area: docs cla: yes This human has signed the Contributor License Agreement. labels Mar 24, 2026
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 is an automated release for the @googleworkspace/cli package, bumping its version to 0.20.1. The core purpose is to propagate a change in how the CLI version is tracked within skill metadata, ensuring all relevant configuration and documentation files reflect the new patch version. This ensures consistency across the project and prepares for the official publication of the updated package.

Highlights

  • Version Release: Released version 0.20.1 of the @googleworkspace/cli package, incorporating a patch change.
  • Version Updates: Updated version numbers across Cargo.lock, Cargo.toml, package.json, and the metadata.version field in numerous SKILL.md files from 0.19.0 or 0.20.0 to 0.20.1.
  • Changelog Update: Added a new entry to CHANGELOG.md detailing the 0.20.1 patch release, which includes moving the CLI version tracking from top-level SKILL.md frontmatter to metadata.
  • Changeset Removal: Removed the .changeset/move-version-to-metadata.md file, indicating the successful application of the described change.
  • Documentation Refinement: Adjusted several internal documentation links within skills/gws-drive/SKILL.md for improved consistency and added a note about using files.export for Google Docs, Sheets, and Slides downloads.
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.

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.

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 24, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.14%. Comparing base (2bfcca9) to head (2ea72c0).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #606   +/-   ##
=======================================
  Coverage   71.14%   71.14%           
=======================================
  Files          42       42           
  Lines       20328    20328           
=======================================
  Hits        14463    14463           
  Misses       5865     5865           

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

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

@jpoehnelt jpoehnelt merged commit 3ac16ee into main Mar 24, 2026
6 checks passed
@jpoehnelt jpoehnelt deleted the changeset-release/main branch March 24, 2026 19:28
@googleworkspace-bot
Copy link
Copy Markdown
Collaborator Author

/gemini review

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: distribution area: docs area: skills cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants