ci: support alpha beta and release candidate versions#708
Conversation
Add qualified release version handling to the draft workflow so alpha, beta, and release candidate versions can be prepared from the selected branch. Publish workflow releases now run from workstation branches and mark qualified versions as GitHub pre-releases instead of latest stable releases. Document the new release flow and record the workflow capability in the changelog.
PR SummaryMedium Risk Overview Adjusts the draft PR creation to work off the selected dispatch branch (checkout and PR base) and updates branch naming to Extends Reviewed by Cursor Bugbot for commit a53d764. Bugbot is set up for automated code reviews on this repo. Configure here. |
|



Background
The Android monorepo release workflow needs fixed pre-release Maven Central versions for partner and internal validation before stable releases. The current draft workflow can only prepare stable patch, minor, or major versions, and the publish workflow only runs from
mainwhile always marking GitHub releases as latest.What Has Changed
Release - Draftwith optionalqualifierinput andbump-type=nonefor moving between alpha, beta, release candidate, and stable versions.release/prep-<version>branch names.Release - Publishto run frommainandworkstation/*, and to mark qualified versions as GitHub pre-releases instead of latest releases.RELEASE.mdaround the current draft and publish workflows, and added a changelog entry for the release workflow capability.Screenshots/Video
N/A — workflow and documentation changes only.
Checklist
Additional Notes
Validated locally with:
trunk checktrunk check --ci./gradlew publishMavenPublicationToMavenLocal -PVERSION=6.0.0-alpha1./gradlew publishMavenPublicationToMavenLocal -PVERSION=6.0.0-alpha1 -c settings-kits.gradle -Pmparticle.kit.mparticleFromMavenLocalOnly=true./gradlew build./gradlew test./gradlew ktlintCheckgit diff --check