 lilleman
|
5a6928750c
|
Give the vulnerability filer a folder of its own, and leave its item's score to rank_todo.py
|
2026-10-14 13:51:22 +02:00 |
|
|
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
|
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
|
117f685939
|
Fail the gate, daily and before each release, on a known vulnerability in the Go release or the module
|
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
|
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
|
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
|
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 |
|
 renovate[bot]
|
f87807adf7
|
Update dependency ubuntu to v26
|
2026-10-05 09:43:17 +02:00 |
|
|
lilleman
|
1b5ed27406
|
Check formatting on the latest Go only, the toolchain that defines it
|
2026-09-21 07:53:11 +02:00 |
|
|
renovate[bot]
|
fad78a8ac0
|
Update actions/checkout action to v7
|
2026-09-21 07:41:36 +02:00 |
|
|
lilleman
|
12b4a095d3
|
Let the test workflow be run by hand
|
2026-09-21 00:30:16 +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
|
1cf8ed502a
|
Cut the release from the changelog heading on a green main instead of a hand-pushed tag
Tests / vet + fmt + tests (pull_request) Successful in 1m7s
Tests / Gitea release from CHANGELOG.md (pull_request) Has been skipped
|
2026-09-16 20:09:38 +02:00 |
|
|
lilleman
|
ea71b3e479
|
Pin the categories each shipped category reads
|
2026-09-16 20:09:38 +02:00 |
|
|
lilleman
|
265bd05dfc
|
Define a patch, disambiguate the Versioning table, name the changelog check, and keep the gate claims true
Tests / vet + fmt + tests (pull_request) Successful in 1m2s
|
2026-09-16 19:49:55 +02:00 |
|
|
lilleman
|
7bf3da807c
|
Settle the compatibility contract, the changelog and the tag-published Gitea release
Tests / vet + fmt + tests (pull_request) Successful in 1m7s
|
2026-09-16 19:29:44 +02:00 |
|
|
lilleman
|
2d28220869
|
Diff the whole push range and de-duplicate the gate-skip note
Tests / vet + fmt + tests (pull_request) Failing after 3s
|
2026-09-03 22:36:48 +02:00 |
|
|
lilleman
|
cc15bdd1d9
|
Run the merge gate only for changes its tests read
Tests / vet + fmt + tests (pull_request) Successful in 1m4s
|
2026-09-03 22:30:02 +02:00 |
|
|
lilleman
|
d44c941a92
|
Make the CI gate work on Gitea by building instead of bind-mounting
Tests / vet + fmt + tests (pull_request) Successful in 27s
Tests / vet + fmt + tests (push) Successful in 6s
|
2026-09-01 20:33:04 +02:00 |
|
 M
|
4ad26970d8
|
Report both Go versions even when the first fails
|
2026-08-28 12:39:03 +02:00 |
|
|
M
|
e7bd363519
|
Run the tests in CI as a merge gate
|
2026-08-28 12:39:03 +02:00 |
|