release

Release artifacts

Nothing generated is committed here. Build outputs and size analyses are large, machine-specific, and reproducible from the source — §33 of the release process says not to commit them, so this directory holds only instructions.

Building the candidate

flutter build apk --release

flutter build apk --release --split-per-abi

flutter build appbundle --release

Outputs land in apps/guitar_practice_app/build/app/outputs/.

Size analysis

flutter build apk --release --analyze-size --target-platform=android-arm64

The JSON is written to ~/.flutter-devtools/apk-code-size-analysis_NN.json (about 8 MB) and is deliberately untracked. To read it:

dart devtools --appSizeBase=<path to the json>

Signing

Release builds fall back to debug keys unless apps/guitar_practice_app/android/key.properties exists. See the repository README. That file, and any keystore, must never be committed.

Release notes

Per-release notes live beside this file, e.g. v0.1.0-beta.1.md. They are the text used for the GitHub release.

Screenshots

Screenshots are rendered from the real widgets, never mocked up:

cd apps/guitar_practice_app && flutter test test/screenshots_test.dart --tags screenshots --update-goldens

python tool/optimize_screenshots.py

Publishing checklist

1. Configure signing (above) and rebuild the artifacts
2. Generate SHA256SUMS.txt next to them
3. Update CHANGELOG.md
4. Tag, and attach the split APKs, the universal APK and the checksums
5. Keep the release a prerelease until it has been installed and opened from the published artifact, not from a local build