chore: preparing for 1.0 RC version

[ishymko]

1. Run release-please on 1.0-dev and set target-branch in the GitHub Action.
2. Use advanced configuration to specify pre-release versioning ("prerelease": true and "prerelease-type": "alpha"), this is going to result in 1.0.0a0 (see here package for v1.0.0-alpha.0 tag.
3. python-publish.yml workflow was disabled as a safety measure in case release-please goes crazy with this config.

For now do not specify last-release-sha explicitly (docs), will check the behavior first, changelog will have to be created manually most likely either way.

[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 establishes the foundational configuration for automated release management using release-please, specifically targeting the upcoming 1.0 release candidate. It sets up pre-release alpha versioning and defines the structure for release notes, streamlining the process for future releases.

Highlights

• Release Configuration: Configured release-please to automate the release process, specifically for the upcoming 1.0 release candidate.
• Pre-release Versioning: Enabled pre-release versioning with prerelease: true and set the prerelease-type to alpha, which will generate versions like 1.0.0a0.
• Custom Changelog Path: Specified a dedicated changelog file, CHANGELOG-1.0.md, for release notes related to the 1.0 series.
• Manifest Initialization: An empty .release-please-manifest.json file was added to track release history and state.

Changelog

• .release-please-manifest.json
  • Initialized the release manifest file with an empty JSON object.
• release-please-config.json
  • Configured the release type as 'python'.
  • Enabled pre-release versioning.
  • Set the pre-release type to 'alpha'.
  • Specified 'CHANGELOG-1.0.md' as the changelog path.
  • Defined the package scope for the current directory.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/release-please.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 configuration files for release-please to automate the release process for the upcoming 1.0 version. The configuration correctly sets up a Python pre-release strategy for creating alpha versions. The changes are straightforward and well-aligned with the goal of preparing for a 1.0 release. I have one minor suggestion regarding the changelog file path for consideration.