feat: add release-please configuration and manifest with initial version 0.0.1

[oxddr]

This should hopefully fix broken release workflow.

[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 integrates release-please into the repository to streamline and automate the software release process. By adding the necessary configuration and manifest files, it establishes a foundation for consistent versioning and release management, which is intended to resolve existing issues with the release workflow.

Highlights

• Release Automation: Introduced release-please to automate the release process, aiming to fix a previously broken release workflow.
• Configuration Files: Added two new configuration files: .release-please-manifest.json and release-please-config.json.
• Initial Versioning: Set the initial project version to 0.0.1 within the release-please manifest.

Changelog

• .release-please-manifest.json
  • Added a new file to track the current version of the project.
• release-please-config.json
  • Added a new file to configure release-please behavior, including release type and version bumping rules.

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 configuration for release-please to automate releases. It adds a release-please-config.json file to define the release strategy and a .release-please-manifest.json to track the initial version. The configuration is standard and appears correct for a simple project, setting up version bumping for pre-major releases according to semantic versioning conventions. I have reviewed the changes and found no issues that meet the required severity threshold for comments.

_{Note: Security Review has been skipped due to the limited scope of the PR.}