Skip to content

RELEASING.md

Latest commit

 

History

History
81 lines (60 loc) · 1.96 KB

RELEASING.md

File metadata and controls

81 lines (60 loc) · 1.96 KB

Release process

  • Collect changes in release branch

    # If it does not exist, create a release branch
git checkout -b releases/2026.1

# If it exists, merge latest changes
git checkout releases/2026.1
git merge dev

  • Optional: update translations

    git commit --all --message "Import latest translations"

  • Change version code and name in build.gradle.kts

  • Update CHANGELOG.md

    ./insert-next-release.sh build.gradle.kts CHANGELOG.md

  • Commit with the suggested message and push

    git commit --all --message "Prepare version 2026.1.1 (23260101)"
git push --set-upstream origin releases/2026.1

  • If it does not exist, create a merge request against main

  • Check build succeeds, tests are green and lint output is as expected

Play Store (testing + production)

  • bundlePureRelease

Alpha

  • Publish to alpha channel
  • Test update on test device

Beta

  • Tag release commit

    git tag v2026.1.2
git push origin v2026.1.2
git checkout dev
git merge releases/2026.1
git push origin dev

  • Promote to beta channel

  • Create or update preview release post on forum

Production

  • bundleAmazonRelease

  • Merge release pull request to main

  • Download universal APK from Play Store

  • Create GitHub release

    • title like SeriesGuide 2026.1.2
    • get release notes from CHANGELOG.md
    • attach APK

  • Prepare release post on forum

  • Promote to production

  • Publish to Amazon App Store

  • Publish release post on forum

  • Post on Mastodon

  • Merge changes to dev branch

    git checkout dev
git merge --no-ff releases/2026.1