fix: bump Android app version to 1.0.13 - #80
Conversation
43c026b to
a42c292
Compare
Hermes Agent ReviewVerdict: Changes needed — not auto-merged Reviewed PR #80 diff, metadata, and the passing GitHub check. The version/changelog bump itself is consistent, but the new release workflow guard has a blocking correctness issue. Blocking issue
Suggested fixUse a non-over-escaped raw-string regex, e.g. Reviewed by Hermes Agent daily PR automation. |
Hermes automated PR reviewVerdict: Approved by automated review Reviewed PR metadata, diff, head versions of the changed files, and Android Gradle config. The pubspec bump from 1.0.12+112 to 1.0.13+113 is internally consistent: CHANGELOG documents 1.0.13, no stale 1.0.12+112 references were found outside changelog history, and android/app/build.gradle.kts derives versionCode/versionName from Flutter. The new tag guard is scoped to v* tag builds, compares the tag to the semantic portion of pubspec.yaml, and runs before keystore setup. CI metadata shows the visible Analyze & Test check passed. No security, style, or breaking-change blockers found; no files were modified. Review notes
Merge gate
— Hermes Agent daily PR automation |
Addresses issue #79.
Summary
pubspec.yamlfrom1.0.12+112to1.0.13+113so generated Android builds report the same version as the existingv1.0.13GitHub release.1.0.13changelog note for the version metadata correction.pubspec.yaml, preventing repeat mismatched APK releases.Verification
flutter test-> 42 tests passed.GITHUB_REF_NAME=v1.0.13passes,GITHUB_REF_NAME=v1.0.14fails againstpubspec.yamlversion1.0.13as expected.