fix: use changeset tag instead of publish, defer npm publishing to cargo-dist

[jpoehnelt]

Problem

The release-changesets.yml workflow uses pnpm changeset publish which attempts to publish @googleworkspace/cli directly to npm when no pending changesets exist. This fails with ENEEDAUTH because npm publishing should be handled by cargo-dist's release.yml, not by changesets.

Additionally, .github/labeler.yml has a YAML parse error — label names containing colons need to be quoted.

Fix

Publishing

Separate concerns between the two release workflows:

• Changesets (release-changesets.yml) — version management only. Uses pnpm changeset tag to bump versions and push git tags.
• cargo-dist (release.yml) — binary distribution + npm publishing. Triggered by the git tag pushed by changesets.

Labeler

Quote all label names containing colons in labeler.yml.

Changes

• release-changesets.yml: pnpm changeset publish → pnpm changeset tag, removed id-token permission and NPM_TOKEN env var
• package.json: added "private": true to prevent accidental direct npm publishing
• labeler.yml: quoted label names containing colons (e.g. area: schema → "area: schema")

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0780a70

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[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 refines the publishing workflow for the @googleworkspace/cli package. By marking the package as private and deferring npm publishing to cargo-dist, it ensures a more controlled and integrated release process, preventing direct npm publishing and aligning with a changeset-based tagging strategy.

Highlights

• Publishing Strategy: The project's publishing mechanism has been updated to defer npm publishing to cargo-dist, aligning with a strategy to use changeset tags instead of direct npm publish.
• Package Privacy: The package.json file has been configured with "private": true to prevent accidental or unintended publishing of the package to npm.

Changelog

• package.json
  • Added "private": true to prevent accidental publishing.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/release-changesets.yml

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

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request modifies package.json to set the private property to true. This action prevents the package from being published to the npm registry, which is consistent with the pull request's objective to delegate publishing to cargo-dist. The change is self-contained and I have no further feedback.