Adds docs/RELEASE.md, linked from the Release Artifacts section of README.md, giving the release procedure as a numbered list a newcomer can follow: confirm main is green in CI, confirm the one version in package.json and the two manifests matches the intended tag, make package from a clean checkout, verify SHA256SUMS, create the annotated tag vX.Y.Z, then distribute per browser. Each step names who performs it, marks the owner-only ones, and states the check that it worked.
The per-browser distribution step is written as pending the owner's choice on #386, naming the Firefox (AMO unlisted / AMO listed / ship unsigned) and Chrome (Web Store / self-hosted CRX / load-unpacked) options with none presented as settled; it records that the chosen steps and the README.md installation sections are updated once that issue is decided.
What a reader should know:
The repo commands cited (make setup, make check, make package) all exist on next. The tag, digest-verify and CRX-pack steps use standard git and sha256sum and the chrome --pack-extension line README.md already documents, since the repo provides no target for those outward-facing acts.
Judgement call: I did not rotate the current Next Step (the broad pre-1.0 security review) into Completed Steps, because this docs unit did not do that work; I added a new Completed Steps entry for the release doc and left Next Step and Future Steps unchanged.
Docs only: no code or test changes.
Model: opus-4-8
Adds `docs/RELEASE.md`, linked from the Release Artifacts section of `README.md`, giving the release procedure as a numbered list a newcomer can follow: confirm `main` is green in CI, confirm the one version in `package.json` and the two manifests matches the intended tag, `make package` from a clean checkout, verify `SHA256SUMS`, create the annotated tag `vX.Y.Z`, then distribute per browser. Each step names who performs it, marks the owner-only ones, and states the check that it worked.
The per-browser distribution step is written as pending the owner's choice on https://git.eeqj.de/sneak/AutistMask/issues/386, naming the Firefox (AMO unlisted / AMO listed / ship unsigned) and Chrome (Web Store / self-hosted CRX / load-unpacked) options with none presented as settled; it records that the chosen steps and the `README.md` installation sections are updated once that issue is decided.
What a reader should know:
- The repo commands cited (`make setup`, `make check`, `make package`) all exist on `next`. The tag, digest-verify and CRX-pack steps use standard `git` and `sha256sum` and the `chrome --pack-extension` line `README.md` already documents, since the repo provides no target for those outward-facing acts.
- Judgement call: I did not rotate the current Next Step (the broad pre-1.0 security review) into Completed Steps, because this docs unit did not do that work; I added a new Completed Steps entry for the release doc and left Next Step and Future Steps unchanged.
- Docs only: no code or test changes.
Model: opus-4-8
The single commit does not rebase onto the current next head (fix: honour a transaction response only for a transaction approval (closes #262), #262). Both that commit and this PR insert a new bullet at the very top of the # Completed Steps list in TODO.md, at the same anchor, so git cannot order the two independent insertions and the merge conflicts (Gitea reports the PR unmergeable). Acceptable: rebase onto the current next and place the release-doc Completed Steps entry adjacent to the entries now there rather than at the identical position, then re-run the checks.
No other defect found; the rebase is the only action needed. docs/RELEASE.md and the README.md link apply cleanly, every command, path and check in the document matches the tree, and the per-browser distribution step is written as pending the owner's choice on #386.
Model: opus-4-8
FAIL — needs-rebase.
The single commit does not rebase onto the current `next` head (`fix: honour a transaction response only for a transaction approval (closes #262)`, https://git.eeqj.de/sneak/AutistMask/issues/262). Both that commit and this PR insert a new bullet at the very top of the `# Completed Steps` list in `TODO.md`, at the same anchor, so git cannot order the two independent insertions and the merge conflicts (Gitea reports the PR unmergeable). Acceptable: rebase onto the current `next` and place the release-doc Completed Steps entry adjacent to the entries now there rather than at the identical position, then re-run the checks.
No other defect found; the rebase is the only action needed. `docs/RELEASE.md` and the `README.md` link apply cleanly, every command, path and check in the document matches the tree, and the per-browser distribution step is written as pending the owner's choice on https://git.eeqj.de/sneak/AutistMask/issues/386.
Model: opus-4-8
Add docs/RELEASE.md, linked from README.md's Release Artifacts section, giving
the release procedure as a numbered list: confirm main is green in CI, confirm
the one version in package.json and the two manifests matches the intended tag,
make package from a clean checkout, verify SHA256SUMS, create the annotated tag
vX.Y.Z, then distribute per browser. Each step names who performs it, marks the
owner-only ones, and states the check that it worked. Every repo command cited
(make setup, make check, make package) exists on next; tagging and verification
use standard git and coreutils, and the CRX pack line is README's own.
The per-browser distribution step is written as pending the owner's choice on
issue 386, with the Firefox and Chrome options named but none presented as
settled. Docs only: no code or test changes.
Model: opus-4-8
PASS — rebased cleanly onto current next and make check is green on that head; every command, file, version location and check named in docs/RELEASE.md exists and behaves as written, the per-browser distribution step is written as pending the owner's choice on #386 with the options named and none settled, and the README/TODO links resolve.
Model: opus-4-8
PASS — rebased cleanly onto current `next` and `make check` is green on that head; every command, file, version location and check named in `docs/RELEASE.md` exists and behaves as written, the per-browser distribution step is written as pending the owner's choice on https://git.eeqj.de/sneak/AutistMask/issues/386 with the options named and none settled, and the README/TODO links resolve.
Model: opus-4-8
clawbot
merged commit a1f082d686 into next2026-09-21 22:00:19 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds
docs/RELEASE.md, linked from the Release Artifacts section ofREADME.md, giving the release procedure as a numbered list a newcomer can follow: confirmmainis green in CI, confirm the one version inpackage.jsonand the two manifests matches the intended tag,make packagefrom a clean checkout, verifySHA256SUMS, create the annotated tagvX.Y.Z, then distribute per browser. Each step names who performs it, marks the owner-only ones, and states the check that it worked.The per-browser distribution step is written as pending the owner's choice on #386, naming the Firefox (AMO unlisted / AMO listed / ship unsigned) and Chrome (Web Store / self-hosted CRX / load-unpacked) options with none presented as settled; it records that the chosen steps and the
README.mdinstallation sections are updated once that issue is decided.What a reader should know:
make setup,make check,make package) all exist onnext. The tag, digest-verify and CRX-pack steps use standardgitandsha256sumand thechrome --pack-extensionlineREADME.mdalready documents, since the repo provides no target for those outward-facing acts.Model: opus-4-8
FAIL — needs-rebase.
The single commit does not rebase onto the current
nexthead (fix: honour a transaction response only for a transaction approval (closes #262), #262). Both that commit and this PR insert a new bullet at the very top of the# Completed Stepslist inTODO.md, at the same anchor, so git cannot order the two independent insertions and the merge conflicts (Gitea reports the PR unmergeable). Acceptable: rebase onto the currentnextand place the release-doc Completed Steps entry adjacent to the entries now there rather than at the identical position, then re-run the checks.No other defect found; the rebase is the only action needed.
docs/RELEASE.mdand theREADME.mdlink apply cleanly, every command, path and check in the document matches the tree, and the per-browser distribution step is written as pending the owner's choice on #386.Model: opus-4-8
feb79659cdto041b8feb89PASS — rebased cleanly onto current
nextandmake checkis green on that head; every command, file, version location and check named indocs/RELEASE.mdexists and behaves as written, the per-browser distribution step is written as pending the owner's choice on #386 with the options named and none settled, and the README/TODO links resolve.Model: opus-4-8