26 Commits

Author	SHA1	Message	Date
lilleman	15965e7a77	State the filer's contract with the plan where it is read, name the step an outage fails, and mark an unfixed vulnerability by name	2026-10-14 13:51:22 +02:00
lilleman	6a7da08002	Answer architecture round 4: 0 🔴, 0 🟡; an entry with no summary files without a bare colon	2026-10-14 13:51:22 +02:00
lilleman	9049f90cc5	Answer architecture round 3: 0 🔴, 2 🟡; a plan-only change runs the test that pins the plan's shape, and a module record carries its own path	2026-10-14 13:51:22 +02:00
lilleman	2d86f4f0c0	Answer architecture round 2: 1 🔴, 3 🟡; read the report and edit the plan in two functions, propose only while no pull request is open, and test filing into the repository's own todo.md	2026-10-14 13:51:22 +02:00
lilleman	273dd45128	Answer architecture round 1: 0 🔴, 5 🟡; a job of its own that only releases wait for, filing each vulnerability atop the plan by a pull request, a recorded decision, one gate list, and Renovate on the go run tools	2026-10-14 13:51:22 +02:00
lilleman	3d0d7ef180	Test filing each known vulnerability as a security item atop the next release	2026-10-14 13:51:22 +02:00
lilleman	508e93d11a	Answer architecture round 1: 0 🔴, 3 🟡; copy the image to Docker Hub in a job of its own, give the registries their own decision, and name the narrowest token	2026-10-14 11:33:08 +02:00
lilleman	f3fbbac0d9	Push the image to Docker Hub beside GHCR, so docker run larvit/fejkdata works	2026-10-14 11:33:08 +02:00
lilleman	717f9f2abc	Drop the AUR until it reopens registration, and plan it as item 252	2026-10-14 09:49:01 +02:00
lilleman	2885f7b571	Answer prose round 1: 0 🔴, 4 🟡; name the package-repository checks, list the release secrets, and point each sentence at its actor	2026-10-14 09:49:01 +02:00
lilleman	a1f25e4138	Answer stability round 2: 0 🔴, 1 🟡; test that main() passes on a failed publish's exit code	2026-10-14 09:49:01 +02:00
lilleman	b9ae602399	Answer stability round 1: 0 🔴, 3 🟡; fail when the latest release can't be read, build every platform's binaries when Go changes, and test main() and the Unreleased heading	2026-10-14 09:49:01 +02:00
lilleman	a82279c6a4	Answer product-owner round 1: 0 🔴, 1 🟡; check the apk repository on Alpine 3.24's apk-tools 3, and say how macOS runs a downloaded binary	2026-10-14 09:49:01 +02:00
lilleman	895c0e977f	Answer architecture round 4: 0 🔴, 1 🟡; run the repository checks on every file they read, and check each repository installs the release's own version	2026-10-14 09:49:01 +02:00
lilleman	e6e06d007b	Answer architecture round 3: 0 🔴, 4 🟡; keep signing keys out of image layers, and build and install from the package repositories in the gate with throwaway keys	2026-10-14 09:49:01 +02:00
lilleman	f08182fb94	Answer architecture round 2: 1 🔴, 0 🟡; self-host signed apt, dnf and apk repositories on GitHub Pages in place of Cloudsmith, and keep an older tag's image while leaving latest alone	2026-10-14 09:49:01 +02:00
lilleman	cc7d4fb972	Answer architecture round 1: 0 🔴, 7 🟡; build with the gate's Go, guard single-version channels on older tags, record the Cloudsmith tie, and return the tag from publish()	2026-10-14 09:49:01 +02:00
lilleman	e67c858d41	Ship prebuilt binaries, deb, rpm and apk packages on Cloudsmith, a GHCR image, and Homebrew, Scoop and AUR packages with each release	2026-10-14 09:49:01 +02:00
lilleman	478a962f34	Test that a published release names its tag to CI, and that the gate checks the packaging config	2026-10-14 09:49:01 +02:00
lilleman	5bd978d2a1	Answer stability round 1: items 191 and 192 leave the plan, the decision and item 193 name the size test, and the test's temp dir is tmp	2026-10-12 17:50:30 +02:00
lilleman	870082c12f	Read an existing tag through git/ref/tags in publish_release.py, following an annotated tag to its commit	2026-10-12 17:50:30 +02:00
lilleman	2c9ff3b014	Test that the shipped data stays under 100 MiB and that publish_release.py stops on a tag at another commit, both in the gate	2026-10-12 17:50:30 +02:00
lilleman	fab6ab4f2e	Move the project to GitHub, where a stranger can file an issue and open a PR	2026-09-21 00:30:16 +02:00
lilleman	16f2e96fe8	Refuse a release whose tag sits elsewhere, pin a typed nullable column and a relative reference in the reads test, and narrow the pin's claim to template formats	2026-09-16 20:17:50 +02:00
lilleman	1cf8ed502a	Cut the release from the changelog heading on a green main instead of a hand-pushed tag	2026-09-16 20:09:38 +02:00
lilleman	7bf3da807c	Settle the compatibility contract, the changelog and the tag-published Gitea release	2026-09-16 19:29:44 +02:00