chore: move release workflows to main

[sasha-gitg]

No description provided.

[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 introduces automated release management for the project by integrating release-please. It establishes a configuration for generating prerelease alpha versions for the google-adk Python package, streamlining the versioning process and ensuring consistent changelog generation based on commit types.

Highlights

• Release Automation Setup: Configured release-please for automated versioning and changelog generation for the google-adk Python project.
• Prerelease Versioning: Set up the release process to generate prerelease alpha versions, with GitHub releases currently skipped.

🧠 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.

Ignored Files

• Ignored by pattern: .github/workflows/** (6)
  • .github/workflows/release-v2-cherry-pick.yml
  • .github/workflows/release-v2-cut.yml
  • .github/workflows/release-v2-finalize.yml
  • .github/workflows/release-v2-please.yml
  • .github/workflows/release-v2-publish.yml
  • .github/workflows/v2-sync.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.

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. ↩

[adk-bot]

Response from ADK Triaging Agent

Hello @sasha-gitg, thank you for creating this PR!

Could you please add a description to this PR explaining the changes and the motivation behind them? Additionally, could you please include a testing plan to help reviewers understand how to verify the changes?

This information will help reviewers to review your PR more efficiently. Thanks!

[gemini-code-assist]

Code Review

This pull request introduces new release-please configuration files for a v2 release track. The setup correctly defines a Python prerelease workflow with an initial alpha version. The changelog-sections are well-defined, focusing on user-facing changes while hiding internal commit types.

[gemini-code-assist]

The skip-github-release is set to true. While this is common for alpha prereleases, please confirm if the intention is to eventually create GitHub releases for v2 versions. If so, this setting will need to be updated when moving to stable v2 releases. If v2 is intended solely for internal or prerelease purposes without public GitHub releases, then this setting is appropriate.

[adk-bot]

Thank you @sasha-gitg for your contribution! 🎉

Your changes have been successfully imported and merged via Copybara in commit b6185f7.

Closing this PR as the changes are now in the main branch.