release/signing/apple-app
Release artifacts are signed
Implements release/signing for the apple-app artifact: it runs when the release publishes one (see artifacts).
| Severity | error |
| Tiers | 1 |
| Artifact | apple-app |
| Scope | root |
| Kind | outcome |
| Source | library v0.3.1 |
| Selected by | fleetlint-recommended@v0.3.1 |
Requirement
The build is code-signed with a Developer ID or distribution identity on export (xcodebuild -exportArchive with a signing identity, codesign, fastlane gym/match, flutter build ipa --export-options-plist); a macOS download is notarized and stapled (notarytool submit, stapler).
Why
Checksums prove integrity; only a signature proves who built it.
Capability applies when
release.exists || repo.artifacts.size() > 0Fix
Export with a signing identity (xcodebuild -exportArchive -exportOptionsPlist with the distribution certificate from CI secrets, or fastlane match + gym); for a macOS download add notarytool submit --wait and stapler staple.
Agent instruction: Use the artifact’s own signing format when it 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://developer.apple.com/documentation/security/notarizing-macos-software-before-distribution
Generated by fleetlint docs from catalog v0.3.1.