Skip to content

chore: release versions#647

Merged
jpoehnelt merged 1 commit intomainfrom
changeset-release/main
Mar 31, 2026
Merged

chore: release versions#647
jpoehnelt merged 1 commit intomainfrom
changeset-release/main

Conversation

@googleworkspace-bot
Copy link
Copy Markdown
Collaborator

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

Patch Changes

  • 86c08cf: Remove cargo-dist; use native Node.js fetch for npm binary installer

    Replaces the cargo-dist generated release pipeline and npm package with:

    • A custom GitHub Actions release workflow with matrix cross-compilation
    • A zero-dependency npm installer using native fetch() (Node 18+)
    • Removes axios, rimraf, detect-libc, console.table, and axios-proxy-builder dependencies from the published npm package

@jpoehnelt jpoehnelt merged commit f4ee658 into main Mar 31, 2026
27 checks passed
@jpoehnelt jpoehnelt deleted the changeset-release/main branch March 31, 2026 17:20
@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 performs a version release for the @googleworkspace/cli package. It includes a significant architectural shift in the release pipeline by replacing cargo-dist with a custom GitHub Actions workflow and streamlining the npm package installation process to be zero-dependency, leveraging native Node.js capabilities.

Highlights

  • Release Version Update: Bumped the version of @googleworkspace/cli and related components to 0.22.4.
  • Dependency Management: Updated several Rust dependencies in Cargo.lock, including hyper, wasm-bindgen, and uuid, while removing the unused pin-utils crate.
  • Infrastructure Changes: Removed cargo-dist in favor of a custom GitHub Actions release workflow and implemented a zero-dependency npm installer using native Node.js fetch.
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 31, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.86%. Comparing base (c7c6646) to head (a04a186).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #647      +/-   ##
==========================================
+ Coverage   70.84%   70.86%   +0.01%     
==========================================
  Files          44       44              
  Lines       20646    20646              
==========================================
+ Hits        14626    14630       +4     
+ Misses       6020     6016       -4     

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

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the @googleworkspace/cli to version 0.22.4 and replaces the cargo-dist release pipeline with a custom GitHub Actions workflow and a zero-dependency npm installer using native fetch(). These changes result in the removal of several npm dependencies, such as axios and rimraf. The PR also includes various Rust dependency updates and synchronizes the version across all package manifests and skill metadata files. I have no feedback to provide as there are no review comments to assess.

@github-actions github-actions bot added the gemini: reviewed Gemini Code Assist has reviewed the latest changes label Mar 31, 2026
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. crate: google-workspace gemini: reviewed Gemini Code Assist has reviewed the latest changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants