Skip to content

Add tagged releases, reproducibility CI and a Zapstore manifest - #1

Open
Kilombino wants to merge 1 commit into
AstrolexisAI:mainfrom
Kilombino:release-y-zapstore
Open

Add tagged releases, reproducibility CI and a Zapstore manifest#1
Kilombino wants to merge 1 commit into
AstrolexisAI:mainfrom
Kilombino:release-y-zapstore

Conversation

@Kilombino

Copy link
Copy Markdown

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.

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.
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