Repository navigation
chore: signed provenance for release apk - #358
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
actions/attestand adds the provenance to the build artifact asevcc-<ver>-fdroid.apk.intoto.jsonl. The attestation is also stored on GitHub.Verify a download
TODO
mainor via manual dispatch and verify the artifact, the attestation step doesn't run on PRs🤖 Generated with Claude Code