BuildAndroidRelease, BuildAndroidApk, and BuildLinuxRelease in ci/main.go now accept an optional commitHash parameter and pass --dart-define=GIT_HASH=<hash> to flutter
PublishAndroid and DeployApk/DeployLinux thread the hash through to the build functions
publish-android and build-android-bundle tasks in Taskfile.yml now capture git rev-parse --short HEAD and forward it as --commit-hash
Previously, Dagger-based builds (Play Store AAB, direct APK deploy, Linux release) did not inject GIT_HASH, so _gitHash in about_screen.dart was always empty and the "Git Commit" row was never shown. Local fvm-based builds already had the --dart-define=GIT_HASH=... flag; this aligns the Dagger builds to match.
Test plan
flutter analyze — no issues
flutter test test/unit test/widget — all 459 tests pass
Pre-commit hooks passed on commit
CI: Dagger full check suite via task check-dagger
## Summary
- `BuildAndroidRelease`, `BuildAndroidApk`, and `BuildLinuxRelease` in `ci/main.go` now accept an optional `commitHash` parameter and pass `--dart-define=GIT_HASH=<hash>` to flutter
- `PublishAndroid` and `DeployApk`/`DeployLinux` thread the hash through to the build functions
- `publish-android` and `build-android-bundle` tasks in `Taskfile.yml` now capture `git rev-parse --short HEAD` and forward it as `--commit-hash`
Previously, Dagger-based builds (Play Store AAB, direct APK deploy, Linux release) did not inject `GIT_HASH`, so `_gitHash` in `about_screen.dart` was always empty and the "Git Commit" row was never shown. Local `fvm`-based builds already had the `--dart-define=GIT_HASH=...` flag; this aligns the Dagger builds to match.
## Test plan
- [x] `flutter analyze` — no issues
- [x] `flutter test test/unit test/widget` — all 459 tests pass
- [x] Pre-commit hooks passed on commit
- [ ] CI: Dagger full check suite via `task check-dagger`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
BuildAndroidRelease,BuildAndroidApk, andBuildLinuxReleaseinci/main.gonow accept an optionalcommitHashparameter and pass--dart-define=GIT_HASH=<hash>to flutterPublishAndroidandDeployApk/DeployLinuxthread the hash through to the build functionspublish-androidandbuild-android-bundletasks inTaskfile.ymlnow capturegit rev-parse --short HEADand forward it as--commit-hashPreviously, Dagger-based builds (Play Store AAB, direct APK deploy, Linux release) did not inject
GIT_HASH, so_gitHashinabout_screen.dartwas always empty and the "Git Commit" row was never shown. Localfvm-based builds already had the--dart-define=GIT_HASH=...flag; this aligns the Dagger builds to match.Test plan
flutter analyze— no issuesflutter test test/unit test/widget— all 459 tests passtask check-dagger