Ci/release prep

[ChanTsune]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @ChanTsune, 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 prepares the repository for streamlined releases by introducing a release.toml configuration file. This file standardizes the naming convention for release tags and defines the commit message to be used when bumping versions, thereby automating and harmonizing future release procedures.

Highlights

• New Release Configuration: A new release.toml file has been added to the repository, introducing configuration for automated release processes.
• Standardized Tag Naming: The release.toml file defines a standard format for release tags, using {{crate_name}}-{{version}} to ensure consistency across releases.
• Automated Pre-release Commit Message: A default commit message for pre-release version bumps has been configured as :bookmark: Bump {{crate_name}} version to {{version}}, which will be used by release automation tools.

Ignored Files

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

[gemini-code-assist]

Code Review

This pull request introduces a release.toml file to configure the release process, likely using cargo-release. The configuration specifies the format for Git tags and the commit message for version bumps. My review includes one high-severity suggestion to improve the robustness of the release process by explicitly excluding the fuzz crate, which is unlikely to be published and could cause the release to fail.