release/signing/flutter
Release artifacts are signed
Implements release/signing for flutter.
| Severity | error |
| Tiers | 1 |
| Stacks | flutter |
| Scope | root |
| Kind | outcome |
| Source | library v0.2.0 |
| Selected by | fleetlint-recommended@v0.2.0 |
Requirement
The Android build is signed with the release key and verified (apksigner, jarsigner) or signed in the release workflow (a sign-android-release action), and an iOS or macOS build is code-signed on export (xcodebuild -exportArchive, codesign, fastlane gym/match, flutter build ipa --export-options-plist); or a stack-neutral signature: cosign, GoReleaser, gpg.
Why
Checksums prove integrity; only a signature proves who built it.
Capability applies when
release.exists && tagged_workflows().size() > 0Fix
Sign the APK/AAB with the release key and verify it with apksigner (or jarsigner for an AAB) in the release workflow; export iOS builds with a signing identity (flutter build ipa --export-options-plist).
Agent instruction: Use the stack’s signing format when the stack has one. Otherwise add sigstore/cosign-installer and a signing step after the artifacts are built. Files: cosign sign-blob --yes --bundle checksums.txt.sigstore.json checksums.txt and upload the bundle. Container image: cosign sign --yes <image>@<digest> using the digest output of the build step, with id-token: write on the job.
See: https://fleetlint.org/baseline/#releases, https://fleetlint.org/stacks/#flutter--dart, https://docs.flutter.dev/deployment/android#sign-the-app
Generated by fleetlint docs from catalog v0.2.0.