ci: remove obsolete release preparation script

[Mesteriis]

Summary

Remove the old release preparation script now that releases are driven directly from the version already committed on main.

Changes

• remove release:prepare from package.json
• delete scripts/prepare-release.mjs

Why

This script belonged to the old release flow that tried to mutate version files inside GitHub Actions and push back to main. The workflow no longer uses that approach, so the script is dead code.

[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 streamlines the continuous integration process by removing an outdated release preparation script. The script is no longer necessary as the release workflow has been modernized to manage versions directly from the main branch, thereby simplifying the build and deployment pipeline.

Highlights

• Script Removal: The release:prepare script has been removed from package.json.
• File Deletion: The scripts/prepare-release.mjs file, which contained the obsolete release preparation logic, has been deleted.
• Workflow Update: These changes reflect an updated release flow where releases are driven directly from the version committed on main, eliminating the need for mutating version files within GitHub Actions.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• package.json
  • Removed the release:prepare script entry.
• scripts/prepare-release.mjs
  • Deleted the entire script file as it is no longer used.

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 removes an obsolete release preparation script and its corresponding entry in package.json. No security vulnerabilities were found. The changes are straightforward and correctly remove dead code, which is a good maintenance practice, consistent with the new release flow.