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

Patch Changes

• b3669e0: Add hourly cron to generate-skills workflow to auto-sync skills with upstream Google Discovery API changes via PR
• e8d533e: Add workflow to publish OpenClaw skills to ClawHub
• 3b38c8d: Sync generated skills with latest Google Discovery API specs

[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 process for the @googleworkspace/cli package, incrementing its version to 0.3.1. This version bump integrates a new feature that adds a workflow for publishing OpenClaw skills to ClawHub, ensuring that the package's metadata and changelog accurately reflect the latest changes and are prepared for publication.

Highlights

• Version Bump: The @googleworkspace/cli package has been updated from 0.3.0 to 0.3.1 across various configuration files.
• New Feature Release: This release incorporates a new workflow designed to publish OpenClaw skills to ClawHub.

Changelog

• .changeset/publish-skills-workflow.md
  • Removed the changeset file after its content was incorporated into the CHANGELOG.md.
• CHANGELOG.md
  • Added a new entry for version 0.3.1 under @googleworkspace/cli.
  • Included the patch change e8d533e with the description: "Add workflow to publish OpenClaw skills to ClawHub".

Activity

• This pull request was automatically opened by the Changesets release GitHub action.
• It is designed to be updated automatically if more changesets are added to the main branch.
• Merging this PR will trigger the automatic publication of packages 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 contains automated changes for a version bump to 0.3.1. The version has been updated in package.json, Cargo.toml, and Cargo.lock. The CHANGELOG.md has also been updated to reflect this new release. The changes are consistent with a standard release process and appear to be correct.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.40%. Comparing base (3b38c8d) to head (ea34d06).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #62   +/-   ##
=======================================
  Coverage   52.40%   52.40%           
=======================================
  Files          36       36           
  Lines       11693    11693           
=======================================
  Hits         6128     6128           
  Misses       5565     5565           

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