Skip to content

chore: release versions#547

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

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

Conversation

@googleworkspace-bot
Copy link
Collaborator

@googleworkspace-bot googleworkspace-bot commented Mar 18, 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.18.0

Minor Changes

  • 908cf73: feat(gmail): auto-populate From header with display name from send-as settings

    Fetch the user's send-as identities to set the From header with a display name in all mail helpers (+send, +reply, +reply-all, +forward), matching Gmail web client behavior. Also enriches bare --from emails with their configured display name.

  • 6e4daaf: Gmail helpers rollup: mail-builder migration, --attach flag (upload endpoint), +read helper

    • Migrate +send, +reply, +reply-all, and +forward to the mail-builder crate for RFC-compliant MIME construction
    • Add --from flag to +send for send-as alias support
    • Add -a/--attach flag to all mail helpers (+send, +reply, +reply-all, +forward) with mime_guess2 auto-detection, 25MB size validation, and upload endpoint support (35MB API limit vs 5MB metadata-only)
    • Add +read helper to extract message body and headers (text, HTML, or JSON output)
    • Make OriginalMessage.thread_id optional (Option<String>) for draft compatibility
    • RFC 2822 display name quoting is handled natively by mail-builder
    • Introduce UploadSource enum in executor for type-safe upload strategies

Patch Changes

  • 1e90380: fix(gmail): remove dead --attachment arg from +send

    The +send subcommand defined a duplicate "attachment" arg alongside the
    "attach" arg already provided by common_mail_args. Since parse_attachments
    reads "attach", the --attachment flag was silently ignored. Removed the
    dead duplicate.

  • 908cf73: fix(gmail): handle reply-all to own message correctly

    Reply-all to a message you sent no longer errors with "No To recipient remains." The original To recipients are now used as reply targets, matching Gmail web client behavior.

  • 2e909ae: Consolidate terminal sanitization, coloring, and output helpers into a new output.rs module. Fixes raw ANSI escape codes in watch.rs that bypassed NO_COLOR and TTY detection, upgrades sanitize_for_terminal to also strip dangerous Unicode characters (bidi overrides, zero-width spaces, directional isolates), and sanitizes previously raw API error body and user query outputs.

@googleworkspace-bot googleworkspace-bot added area: distribution area: docs cla: yes This human has signed the Contributor License Agreement. labels Mar 18, 2026
@gemini-code-assist
Copy link
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 automates the release process for the @googleworkspace/cli package, bumping its version to 0.18.0. It incorporates significant updates to Gmail helper functionalities, including robust MIME construction and attachment handling, alongside improvements to terminal output sanitization and coloring for a cleaner user experience.

Highlights

  • Gmail Helpers Enhancements: Migrated mail helpers (+send, +reply, +reply-all, +forward) to the mail-builder crate for RFC-compliant MIME construction, added a --from flag for send-as alias support, introduced an -a/--attach flag with mime_guess2 auto-detection and upload endpoint support, and added a +read helper to extract message body and headers.
  • Terminal Output Hygiene: Consolidated terminal sanitization, coloring, and output helpers into a new output.rs module. This fixed raw ANSI escape codes, upgraded sanitize_for_terminal to strip dangerous Unicode characters, and sanitized previously raw API error body and user query outputs.
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.

Copy link
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 is an automated release PR generated by the Changesets action. It updates the version of @googleworkspace/cli to 0.18.0 across package.json, Cargo.toml, and Cargo.lock. The CHANGELOG.md has been updated with the release notes from the consumed changeset files, and flake.lock has been updated accordingly. The changes are consistent with a standard release process and appear to be correct. There are no issues to report.

@github-actions github-actions bot added the gemini: reviewed Gemini Code Assist has reviewed the latest changes label Mar 18, 2026
@codecov
Copy link

codecov bot commented Mar 18, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.06%. Comparing base (908cf73) to head (a5d6c73).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #547   +/-   ##
=======================================
  Coverage   69.06%   69.06%           
=======================================
  Files          42       42           
  Lines       19261    19261           
=======================================
  Hits        13302    13302           
  Misses       5959     5959           

☔ 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 github-actions bot removed the gemini: reviewed Gemini Code Assist has reviewed the latest changes label Mar 18, 2026
@googleworkspace-bot
Copy link
Collaborator Author

/gemini review

@jpoehnelt jpoehnelt merged commit 23ffc33 into main Mar 18, 2026
16 checks passed
@jpoehnelt jpoehnelt deleted the changeset-release/main branch March 18, 2026 15:48
@googleworkspace-bot
Copy link
Collaborator Author

/gemini review

Copy link
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 project to version 0.18.0, introducing several new features and bug fixes. Key enhancements include automatically populating the 'From' header with display names from send-as settings across all Gmail mail helpers, a significant migration of Gmail mail helpers to the mail-builder crate for RFC-compliant MIME construction, and the addition of a robust --attach flag with upload endpoint support and a new +read helper. Bug fixes address a redundant --attachment argument in +send, correct the behavior of 'reply-all' when responding to one's own message, and consolidate terminal sanitization and output helpers to fix ANSI escape code issues and strip dangerous Unicode characters from outputs. The project's version in Cargo.toml, package.json, and Cargo.lock has been incremented, and the flake.lock file has been updated to reflect changes in the Nix package set.

@github-actions github-actions bot added the gemini: reviewed Gemini Code Assist has reviewed the latest changes label Mar 18, 2026
Copy link
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 primarily focuses on releasing version 0.18.0 of the @googleworkspace/cli package. The changes include updating version numbers in Cargo.toml, Cargo.lock, package.json, and CHANGELOG.md, as well as removing the temporary changeset files. The flake.lock file was also updated to reflect new nixpkgs hashes. Based on the provided diffs, no high or critical issues were identified.

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

Labels

area: distribution area: docs cla: yes This human has signed the Contributor License Agreement. 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