 lilleman
|
5aca8a1fe8
|
Record the comprehension check: paired ruling against f90b4d6 rules worse
|
2026-10-14 13:51:22 +02:00 |
|
|
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
|
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
|
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 |
|
 renovate[bot]
|
d849a87205
|
Update golang Docker tag to v1.27.2
|
2026-10-14 12:02:32 +02:00 |
|
|
lilleman
|
6a4162b902
|
Score every plan item's C, how hard it is to get right, in a column after S
|
2026-10-14 11:48:05 +02:00 |
|
|
lilleman
|
f90b4d6498
|
Record the comprehension check: paired ruling against c3cc251 rules same
|
2026-10-14 11:33:08 +02:00 |
|
|
lilleman
|
fbadb99634
|
Answer architecture round 2: 0 🔴, 0 🟡; tie the token choice to the account type, and keep GHCR's reason in the registry decision
|
2026-10-14 11:33:08 +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
|
c3cc251242
|
Record the comprehension check: paired ruling against 891323d rules same
|
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
|
f3e2c6b1bb
|
Release 0.1.0, and add Larvit's copyright line beside Timewave's
|
2026-10-13 00:43:20 +02:00 |
|
|
lilleman
|
b8b4188af7
|
Answer prose round 1: the id bullet sets apart the test series and the real-looking SSNs, the own-data bullet names a path rather than a category, the stdin heading names all it covers, and doc.go's namespace sentence has its subject
|
2026-10-13 00:42:45 +02:00 |
|
|
lilleman
|
5f8d55e2bb
|
Answer product-owner round 2: the reproducible bullet states its goroutine condition, and the table of contents names the Data format heading it links
|
2026-10-13 00:42:45 +02:00 |
|
|
lilleman
|
df46340af2
|
Answer product-owner round 1: the front page's data and id bullets say what ships and what may be real, the Library section links the terms Data defines, and doc.go's synopsis matches the tagline
|
2026-10-13 00:42:45 +02:00 |
|
|
lilleman
|
82fb611c74
|
Open the README with badges, what ships and a table of contents, put the stdin byte rules under a heading of their own, and move the Library section before Data
|
2026-10-13 00:42:45 +02:00 |
|
|
lilleman
|
891323d041
|
Record the paired ruling at 52e0304, better, and 0.1.0's scoring run, shipped under the floor by the 0.1.0 decision, and file isPath as item 251
|
2026-10-12 18:34:15 +02:00 |
|
|
lilleman
|
bf61527363
|
Answer prose round 1: the seed advice says to log a new seed in the error, the doc and the README alike, the changelog says each run takes a new seed, New's failures read in one pass, and the concurrency lines say who draws
|
2026-10-12 18:34:15 +02:00 |
|
|
lilleman
|
e0f5493daa
|
Answer product-owner round 1: the seed docs say a new seed each run, not draws afresh, the README says to log a drawn seed to replay a run, and the changelog names WithSeed and the data options apart
|
2026-10-12 18:34:15 +02:00 |
|
|
lilleman
|
5971037362
|
Test that the fejkdata binary without --seed draws a new seed each run
|
2026-10-12 18:34:15 +02:00 |
|
|
lilleman
|
cde9e354c5
|
Answer architecture round 2: New's doc comment wraps whole, the README's stream needs no seeded, and the system-seed test reports each run's exit code and stderr
|
2026-10-12 18:34:15 +02:00 |
|
|
lilleman
|
8e8fa92e77
|
Answer architecture round 1: Main draws the CLI's default seed and passes it to run, New names every option mistake at once, dataGiven says what it is, and the docs drop seeded where every sequence is
|
2026-10-12 18:34:15 +02:00 |
|
|
lilleman
|
7c0fa4075f
|
Test that New names a nil module beside the missing seed, and that the CLI without --seed draws from the seed Main gives run
|
2026-10-12 18:34:15 +02:00 |
|
|
lilleman
|
9c8a0449ca
|
Record the last chunk's reading cost
|
2026-10-12 18:34:15 +02:00 |
|
|
lilleman
|
90c804f6e6
|
Fail New without WithSeed, naming it, and seed the CLI from the system without --seed
|
2026-10-12 18:34:15 +02:00 |
|
|
lilleman
|
3ae8b9f1b1
|
Test that New without WithSeed fails naming it, that the CLI without --seed draws afresh each run, and seed every test's New
|
2026-10-12 18:34:15 +02:00 |
|
|
lilleman
|
1a5b632b90
|
Answer prose round 1: List gives direct descents only, the library and CLI lines name their verbs, the template line explains its values, the geo line says which places ship, and the README's pointer rule reads in one pass
|
2026-10-12 18:07:39 +02:00 |
|
|
lilleman
|
143311270c
|
Answer product-owner round 1: the release notes link the tagged README, say how to install and pin, name 64-bit targets, List and IsTemplate, the README says a nullable column needs a pointer, and item 89 names the changelog lines it changes
|
2026-10-12 18:07:39 +02:00 |
|
|
lilleman
|
03597c43c7
|
Record the last chunk's reading cost
|
2026-10-12 18:07:39 +02:00 |
|
|
lilleman
|
6220564e33
|
Rewrite the changelog's Unreleased as what v0.1.0 holds
|
2026-10-12 18:07:39 +02:00 |
|
|
lilleman
|
70fdfbd591
|
Answer prose round 1: the README lists the release tooling's tests in the gate, and the decision says the size test checks the premise
|
2026-10-12 17:50:30 +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
|
ca20aff43d
|
Record the last chunk's reading cost
|
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 |
|