Release Process

Current delivery

PR #6 is merged and v1.5.2 was published on 2026-10-02 at a12c46a309f2edfa5e40650509012618bc4716b7, after passing main CI 37058155538 and explicit owner approval. The owner accepted the standalone card in Chrome 154.0.8037.59 (Official Build) (x86_64), macOS. Source ZIP and tar.gz are available; use index.html from the versioned archive.

Previous delivery

PR #3 is merged into main at 5ab4c00 after owner acceptance and passing release-preparation CI. The application version is v1.5.1. GitHub Release v1.5.1 was published on 2026-10-02 after explicit owner confirmation. The tag points to 901807ffe49504b8882d60a8d80c93fcfeccdae2, whose main CI passed. Source ZIP and tar.gz archives are available.

The accepted file is available from the versioned baseline. The earlier v1.5.0 tag belongs to unfinished feature work and must not be moved or treated as this baseline.

Publication procedure

1. Confirm the exact accepted commit and documentation.
2. Require passing CI on the release-preparation head and check the merged main tree.
3. Create a new, unused version tag at the verified main commit after explicit publication approval.
4. Publish GitHub release notes with download instructions, accepted platform and known limitations. GitHub generates source archives; users need only index.html.
5. Verify tag target, release visibility and downloadable contents. Update live Wiki and repository status to reflect actual publication.

A tag alone establishes neither acceptance nor a custom ZIP attachment. Do not describe a release as published until GitHub confirms it.