chore: release

[Dargon789]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: 431a95e

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

This PR includes changesets to release 1 package

Name	Type
google-workspace-developer-tools	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 performs a routine release for the google-workspace-vscode-extension, incrementing its version to 0.6.3. The update incorporates a change that expands the set of hardcoded Google API scopes to include script.container.ui and script.send_mail, enhancing the extension's functionality. The changelog has been updated accordingly, and the temporary changeset file has been removed.

Highlights

• Version Update: The google-workspace-vscode-extension package has been updated to version 0.6.3.
• Scope Expansion: Two new Google API scopes, https://www.googleapis.com/auth/script.container.ui and https://www.googleapis.com/auth/script.send_mail, have been added to the hardcoded scopes for the extension.
• Changelog Integration: The details of the scope additions have been recorded in the CHANGELOG.md for the new 0.6.3 release.
• Changeset Removal: A temporary changeset file, wild-peaches-relate.md, was removed after its content was incorporated into the changelog.

Changelog

• .changeset/wild-peaches-relate.md
  • Removed the temporary changeset file after its content was applied.
• packages/vscode-extension/CHANGELOG.md
  • Updated the changelog to reflect the 0.6.3 release.
  • Documented the addition of new Google API scopes.
• packages/vscode-extension/package.json
  • Incremented the package version to 0.6.3.

Activity

• No specific activity has been recorded for this pull request yet.

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 is for releasing version 0.6.3. The release includes adding two new scopes. However, a critical issue was found related to this change. The new scopes, https://www.googleapis.com/auth/script.container.ui and https://www.googleapis.com/auth/script.send_mail, have not been classified as sensitive or restricted. This is a significant omission as the tool will fail to warn developers about the risks associated with these scopes. I recommend halting this release until the scopes are properly classified to ensure the tool functions as intended.

[gemini-code-assist]

The change being released introduces two new scopes, https://www.googleapis.com/auth/script.container.ui and https://www.googleapis.com/auth/script.send_mail, but fails to classify them.

• script.send_mail allows sending email on the user's behalf, which is a sensitive operation, similar to gmail.send (which is already classified as sensitive in this extension).
• script.container.ui allows displaying web content in sidebars, which can also be a sensitive capability.

Without proper classification, the linter will not warn users about the sensitive nature of these scopes, defeating a core purpose of this extension. This should be addressed before releasing this version.