ci: add cargo-audit workflow for dependency vulnerability scanning

[jpoehnelt]

Adds a new audit.yml GitHub Actions workflow that runs cargo audit to detect known vulnerabilities in Cargo dependencies.

Triggers:

• On changes to Cargo.lock or Cargo.toml files (push/PR to main)
• Daily at 06:00 UTC (scheduled)
• Manual dispatch

Why: The project had no automated vulnerability scanning for its ~200 transitive Cargo dependencies. Known CVEs would go undetected until manually discovered.

Part of supply chain hardening effort.

[changeset-bot]

🦋 Changeset detected

Latest commit: d9f65ad

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@googleworkspace/cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another 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 enhances the project's supply chain security by integrating automated vulnerability scanning for Rust dependencies. By implementing cargo-audit, the project can now proactively identify and address known CVEs within its dependency tree, ensuring a more robust and secure development lifecycle.

Highlights

• Security Hardening: Introduced automated dependency vulnerability scanning using cargo-audit.
• CI Workflow: Added a new GitHub Actions workflow triggered by dependency file changes, daily schedules, and manual dispatch.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/audit.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.

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

[gemini-code-assist]

Code Review

This pull request adds a changeset file to document the addition of a cargo-audit CI workflow for automated dependency vulnerability scanning. The review feedback identifies that the package name used in the changeset is incorrect for a Rust crate and notes that the actual workflow configuration file mentioned in the description is missing from the changes.