Repository navigation
docs(ops): v2.0.0 is released - #124
Merged
Merged
Conversation
OPS-R16 moves the manifest planned → staged → releasable → released, and the release happened: tag v2.0.0, published 2026-09-15, twenty-seven assets. The note records what was checked rather than that a button was pressed. Every publisher manifest and the checksum file were re-verified against the Ed25519 key an installed bundle checks, and each signed checksum was matched against the bytes the page actually serves. The per-architecture Linux manifests point at their own AppImage, which is the thing v1.3.0 got wrong. The releasable note stays, reworded to the past. A status is a sequence, and deleting the record of the previous step leaves a manifest that cannot say how it got here. Signed-off-by: Wessel Verheij <info@nightworks.io> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
operations
awaiting-maintainer
|
github-actions
Bot
added
awaiting-maintainer
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
1 participant
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.
OPS-R16 moves a manifest
planned → staged → releasable → released, and the release happened: tag v2.0.0, published 2026-09-15, 27 assets.https://github.com/beatrax-app/beatrax/releases/tag/v2.0.0
What the note records
Not that a button was pressed — what was checked before it was:
latest-linux.yml→x86_64.AppImage,latest-linux-arm64.yml→arm64.AppImageThat last row is the thing v1.3.0 got wrong, so it is worth stating rather than assuming.
Asset breakdown (27)
8 bundles (both AppImage architectures, the arm64 dmg, the Windows installer, both
.debarchitectures, the Android apk/aab) · 8 publisher manifests · 9 detached signatures · the signed checksum file · the build-provenance attestation.Why the releasable note stays
Reworded to the past rather than deleted. A status is a sequence; a manifest that drops the record of the previous step cannot say how it got here.
integrity.pyandmanifest_check.pyboth clean (373 goals).