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

Patch Changes

• f281797: docs(auth): add manual Google Cloud OAuth client setup and browser-assisted login guidance

  Adds step-by-step guidance for creating a Desktop OAuth client in Google Cloud Console,
  where to place client_secret.json, and how humans/agents can complete browser consent
  (including unverified app and scope-selection prompts).

• ee2e216: Narrow default OAuth scopes to avoid Error 403: restricted_client on unverified apps and add a --full flag for broader access (fixes auth login: first-run OAuth flow can fail with Google 403 restricted_client (unregistered/restricted scopes) #25). Replace the cryptic non-interactive setup error with actionable step-by-step OAuth console instructions (fixes auth setup: ambiguous 'run setup interactively' error with no manual fallback steps #24).

• de2787e: feat(error): detect disabled APIs and guide users to enable them

  When the Google API returns a 403 accessNotConfigured error (i.e., the
  required API has not been enabled for the GCP project), gws now:

  • Extracts the GCP Console enable URL from the error message body.
  • Prints the original error JSON to stdout (machine-readable, unchanged shape
    except for an optional new enable_url field added to the error object).
  • Prints a human-readable hint with the direct enable URL to stderr, along
    with instructions to retry after enabling.

  This prevents a dead-end experience where users see a raw 403 JSON blob
  with no guidance. The JSON output is backward-compatible; only an optional
  enable_url field is added when the URL is parseable from the message.

  Fixes feat: detect disabled APIs and guide users to enable them #31

• 9935dde: ci: auto-generate and commit skills on PR branch pushes

• 4b868c7: docs: add community guidance to gws-shared skill and gws --help output

  Encourages agents and users to star the repository and directs bug reports
  and feature requests to GitHub Issues, with guidance to check for existing
  issues before opening new ones.

• 0603bce: fix: atomic credential file writes to prevent corruption on crash or Ctrl-C

• 666f9a8: fix(auth): support --help / -h flag on auth subcommand

• bcd2401: fix: flatten nested objects in table output and fix multi-byte char truncation panic

• ee35e4a: fix: warn to stderr when unknown --format value is provided

• e094b02: fix: YAML block scalar for strings with #/:, and repeated CSV/table headers with --page-all

  Bug 1 — YAML output: drive#file rendered as block scalar

  Strings containing # or : (e.g. drive#file, https://…) were
  incorrectly emitted as YAML block scalars (|), producing output like:

  kind: |
    drive#file

  Block scalars add an implicit trailing newline which changes the string
  value and produces invalid-looking output. The fix restricts block
  scalar to strings that genuinely contain newlines; all other strings
  are double-quoted, which is safe for any character sequence.

  Bug 2 — --page-all with --format csv / --format table repeats headers

  When paginating with --page-all, each page printed its own header row,
  making the combined output unusable for downstream processing:

  id,kind,name          ← page 1 header
  1,drive#file,foo.txt
  id,kind,name          ← page 2 header (unexpected!)
  2,drive#file,bar.txt
  

  Column headers (and the table separator line) are now emitted only for
  the first page; continuation pages contain data rows only.

• 173d155: fix: add YAML document separators (---) when paginating with --page-all --format yaml

• 214fc18: ci: skip smoketest on fork pull requests

[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 of version 0.2.2 for the @googleworkspace/cli package, incorporating a series of significant enhancements and bug fixes. The changes focus on improving user experience through better authentication documentation, more informative error messages for disabled APIs, and refined output formatting for YAML, CSV, and tables. Additionally, it includes critical fixes for credential file integrity and updates to CI/CD processes, aiming to deliver a more robust and user-friendly command-line interface.

Highlights

• Authentication Documentation: Added comprehensive guidance for manual Google Cloud OAuth client setup and browser-assisted login, including steps for creating a Desktop OAuth client and handling browser consent.
• OAuth Scope Management: Narrowed default OAuth scopes to prevent Error 403: restricted_client on unverified apps and introduced a --full flag for broader access. Improved error messages for non-interactive setup with actionable instructions.
• API Error Handling: Implemented detection for disabled Google APIs (403 accessNotConfigured errors), providing users with the GCP Console enable URL and guidance to retry after enabling, preventing dead-end experiences.
• CI/CD Automation: Configured CI to auto-generate and commit skills on pull request branch pushes and to skip smoketests on fork pull requests.
• Community Guidance: Added community guidance to the gws-shared skill and gws --help output, encouraging repository stars and directing bug reports/feature requests to GitHub Issues.
• Credential File Integrity: Fixed atomic credential file writes to prevent data corruption during crashes or interruptions (e.g., Ctrl-C).
• Auth Subcommand Help: Ensured support for the --help / -h flag on the authentication subcommand.
• Output Formatting Improvements: Flattened nested objects in table output and resolved a panic related to multi-byte character truncation. Also fixed YAML block scalar issues for strings containing # or : and prevented repeated headers when paginating CSV/table output with --page-all.
• YAML Pagination Separators: Added YAML document separators (---) when paginating with --page-all --format yaml for correct multi-document output.
• Unknown Format Warning: Implemented a warning to stderr when an unknown --format value is provided.

Changelog

• .changeset/461e1845e9c8.md
  • Removed changeset file.
• .changeset/9df09438f1eb.md
  • Removed changeset file.
• .changeset/access-not-configured-guidance.md
  • Removed changeset file.
• .changeset/ci-auto-generate-skills.md
  • Removed changeset file.
• .changeset/docs-community-guidance.md
  • Removed changeset file.
• .changeset/fix-atomic-credential-writes.md
  • Removed changeset file.
• .changeset/fix-auth-help-flag.md
  • Removed changeset file.
• .changeset/fix-table-flatten-and-unicode.md
  • Removed changeset file.
• .changeset/fix-unknown-format-warning.md
  • Removed changeset file.
• .changeset/fix-yaml-block-scalar-and-page-all-headers.md
  • Removed changeset file.
• .changeset/fix-yaml-pagination-separators.md
  • Removed changeset file.
• .changeset/skip-smoketest.md
  • Removed changeset file.
• CHANGELOG.md
  • Added release notes for version 0.2.2, detailing various documentation updates, feature enhancements, and bug fixes.
• Cargo.lock
  • Updated the gws package version to 0.2.2.
• Cargo.toml
  • Updated the gws package version to 0.2.2.
• package.json
  • Updated the @googleworkspace/cli package version to 0.2.2.

Activity

• This pull request was automatically generated by the Changesets release GitHub action.
• It serves as a staging ground for the 0.2.2 release of @googleworkspace/cli.
• Merging this PR will trigger the automatic publication of the package to npm.
• The PR will be updated automatically if more changesets are added to the main branch.

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 appears to be an automated release generated by the Changesets action. It correctly bumps the package version from 0.2.1 to 0.2.2 across Cargo.toml, Cargo.lock, and package.json. The CHANGELOG.md has been updated by consolidating individual changeset files, which have been subsequently removed. These changes are consistent with a standard automated release process, and I see no issues.