chore: remove release-as properties

[jonathannorris]

Cleanup: removing release-as properties from release-please config after successfully validating OIDC npm publishing.

[gemini-code-assist]

Summary of Changes

Hello @jonathannorris, 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 focuses on refining the project's release configuration. It removes specific release-as properties that were temporarily introduced for testing purposes related to OIDC npm publishing. With the successful validation of the publishing process, these temporary configurations are now obsolete and have been cleaned up to maintain a streamlined and accurate release setup.

Highlights

• Configuration Cleanup: Removed the release-as properties from the release-please-config.json file for multiple packages, including the root, web, react, angular, nest, and shared packages.
• Temporary Properties Removal: These release-as properties were temporary and used to trigger test releases during the validation of OIDC npm publishing. They are no longer required.

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

The pull request removes the release-as properties from the release-please-config.json file. These properties were used for temporary test releases and are no longer needed. The changes look good and I have identified no issues.