automate version validation with prod test suite

[MaesterChestnut]

No description provided.

[gemini-code-assist]

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

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.

[github-actions]

📝 PRs merging into main branch

Our main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released.

[kaibolay]

Right now we test with the oldest supported stable versions of Gradle, AGP, and GoogleServices and the most recent (non-alpha, non-snapshot) version of all three (Note: As far as I know, GoogleServices doesn't publish any snapshot, alpha, or RC versions):

Gradle	AGP	GoogleServices
oldest supported	oldest supported	oldest supported
latest (incl. rc)	latest (incl. rc)	latest

Maybe we should (also?) test with the latest stable versions of all three? Maybe other combinations also make sense (e.g. "bleeding edge")?

Gradle	AGP	GoogleServices
oldest supported	oldest supported	oldest supported
latest stable	latest stable	latest stable
latest (incl. rc)	latest (incl. rc)	latest stable
latest (incl. snapshot)	latest (incl. alpha)	latest stable

Maybe the additional combinations can be tested automagically each time the tests run - or they can be selected via flags (e.g. --versions=(oldest|stable|rc|bleeding-edge)) or parameters?

[rebehe]

Right now we test with the oldest supported stable versions of Gradle, AGP, and GoogleServices and the most recent (non-alpha, non-snapshot) version of all three (Note: As far as I know, GoogleServices doesn't publish any snapshot, alpha, or RC versions):

Gradle AGP GoogleServices
oldest supported oldest supported oldest supported
latest (incl. rc) latest (incl. rc) latest
Maybe we should (also?) test with the latest stable versions of all three? Maybe other combinations also make sense (e.g. "bleeding edge")?

Gradle AGP GoogleServices
oldest supported oldest supported oldest supported
latest stable latest stable latest stable
latest (incl. rc) latest (incl. rc) latest stable
latest (incl. snapshot) latest (incl. alpha) latest stable
Maybe the additional combinations can be tested automagically each time the tests run - or they can be selected via flags (e.g. --versions=(oldest|stable|rc|bleeding-edge)) or parameters?

VersionUtils does test with the latest stable version - is that sufficient?

[rebehe]

Nice!