release-changelog

Automate Android release notes and version bumps by applying conventional commits to generate changelogs, updating versionCode and versionName in Gradle properties, and drafting Play Store notes. This reduces manual effort and errors during release preparation.

Yes, changelog generation works with GitHub Actions and Gradle-based Android projects. It uses Git tags to orchestrate releases, automatically updating Gradle version metadata and creating GitHub Releases with generated release notes.

Generate Play Store release notes by parsing conventional commits since the last release tag. The workflow scaffolds the extracted changes into Play Store documentation while simultaneously bumping the Android app version metadata.

The best way to update versionCode and versionName is automating the process based on Gradle properties during release. It ensures accurate version metadata updates and creates Git tags to mark the release point reliably.

You need to use Git tags for orchestrating Android app releases when you want to trigger automated changelog generation and version bumps. Tags act as anchors to determine commits since the last release for accurate notes.

Your automated release workflow requires conventional commits for changelog generation because it parses these structured commit messages to accurately determine feature changes and fixes since the last Git tag, ensuring consistent release notes.