Skip to content

chore: signed provenance for release apk - #358

Merged
naltatis merged 1 commit into
mainfrom
chore/signed-release-provenance
Nov 13, 2026
Merged

naltatis merged 1 commit into
mainfrom
chore/signed-release-provenance

Conversation

@naltatis

Copy link
Copy Markdown
Member

pairs with evcc-io/evcc#36132

Releases now ship a signed build provenance attestation next to the F-Droid APK, which is what the OpenSSF Scorecard "Signed-Releases" check looks for. Signing is keyless via Sigstore, so there are no keys or secrets to manage.

  • The F-Droid CI job attests the APK with actions/attest and adds the provenance to the build artifact as evcc-<ver>-fdroid.apk.intoto.jsonl. The attestation is also stored on GitHub.
  • The APK gets its final release name in CI, so the attested subject matches the release asset.
  • Attestation is skipped on pull requests, since forks get no OIDC token.
  • The release skill uploads both files to the draft release.
  • Published releases are immutable, so earlier ones can't be backfilled. The Scorecard rating improves with each new release.

Verify a download

gh attestation verify evcc-<ver>-fdroid.apk --repo evcc-io/app

TODO

  • run the F-Droid job once on main or via manual dispatch and verify the artifact, the attestation step doesn't run on PRs

🤖 Generated with Claude Code

@naltatis
naltatis merged commit ea4020b into main Nov 13, 2026
13 checks passed
@naltatis
naltatis deleted the chore/signed-release-provenance branch November 13, 2026 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant