Add tagged releases, reproducibility CI and a Zapstore manifest - #1
Open
Kilombino wants to merge 1 commit into
Open
Add tagged releases, reproducibility CI and a Zapstore manifest#1Kilombino wants to merge 1 commit into
Kilombino wants to merge 1 commit into
Conversation
The build is already reproducible and the docs page is current, but there is no path from this repository to the binary: the APK lives only on the website, and with no tags an APK cannot be mapped back to a commit. There are three 'Release build N' commits and no tags. - .github/workflows/verify-reproducible.yml rebuilds on a clean runner and prints the unsigned APK's SHA-256 in the job summary. No secrets, never signs. - zapstore.yaml is the publishing manifest, complete except for the npub. - RELEASING.md is the per-release routine and the Zapstore flow.
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.
The build is already reproducible and the docs page is current, but there is no path from this repository to the binary: the APK lives only on the website, and with no tags an APK cannot be mapped back to a commit. There are three 'Release build N' commits and no tags.