ci: add release-please automation with versioned branch workflow

[Jacksunwei]

Summary

• Adds release-please configuration for automated Python releases
• Uses versioned branch workflow (release/vX.Y.Z) to avoid blocking main during release prep
• Includes draft release support for testing before publishing

Files Added

• .github/release-please-config.json - Release-please configuration with draft releases
• .github/.release-please-manifest.json - Version tracking (starting at 0.2.0)
• .github/workflows/cut-release-branch.yml - Creates release branch, bumps version, builds wheel
• .github/workflows/release-please.yml - Creates CHANGELOG PR, draft release when merged
• .github/workflows/publish-pypi.yml - Publishes to PyPI when draft is published

Release Workflow

1. Run "Cut Release Branch" workflow with version (e.g., 0.3.0)
   • Creates release/v0.3.0 branch
   • Bumps version.py and manifest
   • Builds wheel artifact for testing
2. Release-please automatically creates CHANGELOG PR
3. Team tests wheel + reviews CHANGELOG in parallel
4. Merge PR → draft release created
5. Publish draft release → PyPI publish triggered
6. Copybara syncs to main with chore: release X.Y.Z

Requirements

• Add PYPI_TOKEN secret for PyPI publishing

[gemini-code-assist]

Summary of Changes

Hello @Jacksunwei, 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 a comprehensive continuous integration and delivery pipeline designed to streamline the release process for the google-adk-community Python package. By integrating release-please and a versioned branch workflow, it automates version bumping, changelog generation, and the creation of GitHub releases, culminating in automatic publication to PyPI. This setup aims to enhance release consistency and efficiency while maintaining a clear separation between development on main and release preparation.

Highlights

• Automated Release Management: Implements release-please for automated Python package versioning, changelog generation, and GitHub releases.
• Versioned Branch Workflow: Introduces a release/vX.Y.Z branch strategy to manage releases, allowing main to remain unblocked during release preparation.
• PyPI Publishing: Configures GitHub Actions to automatically publish the Python package to PyPI upon a new GitHub release.
• New CI/CD Configuration: Adds release-please configuration files and GitHub Actions workflows for cutting release branches, running release-please, and publishing to PyPI.

🧠 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

• .github/.release-please-manifest.json
  • Initializes the release-please manifest, setting the starting version for the project to 0.2.0.
• .github/release-please-config.json
  • Configures release-please for a Python project, specifying google-adk-community as the package name.
  • Defines the path for the CHANGELOG.md and an extra-file (src/google/adk_community/version.py) to be updated with new versions.
  • Customizes changelog sections based on conventional commit types, making certain types (test, build, ci, style, chore) hidden from the public changelog.

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/cut-release-branch.yml
  • .github/workflows/publish-pypi.yml
  • .github/workflows/release-please.yml

Activity

• The pull request introduces a new, detailed release workflow.
• It outlines the steps from development on main to creating versioned release branches.
• It describes how release-please will automate version bumps and changelog updates via pull requests.
• It specifies that merging these PRs will trigger GitHub releases and subsequent PyPI publishing.
• A requirement for a PYPI_TOKEN secret for PyPI publishing is noted.

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 release-please automation for managing Python package releases. The configuration is well-structured and follows a versioned branch workflow, which is a great strategy. I've made one suggestion to use a more idiomatic configuration option in the release-please-config.json file to improve clarity. Otherwise, the changes look good.

[gemini-code-assist]

For the python release type, it's more idiomatic to use the version_file property to specify the file containing the version string. While extra-files works, version_file is more specific to the Python release strategy and makes the configuration clearer about its intent to update the Python package version.

      "version_file": "src/google/adk_community/version.py",