Answer prose round 1: 0 🔴, 4 🟡; name the package-repository checks, list the release secrets, and point each sentence at its actor
This commit is contained in:
+10
-9
@@ -903,7 +903,7 @@ By the maintainer's decision of 2026-10-09, every 0.1.0 chunk ships under the fl
|
||||
|
||||
Shipped under that decision: item 89, the last of 0.1.0, at 52e0304. Its paired ruling against 90ffcff was better. The release's scoring run read Navigation 7.00, Locality 5.75, Shape 6.38, Self-sufficiency 6.50 and overall 6.25; its seats named places items 170 to 172 and 178 hold, and `isPath`, filed as item 251.
|
||||
|
||||
Shipped under the floor by the maintainer's decision of 2026-10-13: item 58, prebuilt binaries and packages, as the distribution of 0.1.0 rather than a 0.2.0 item. It changes no Go code.
|
||||
Shipped under the floor by the maintainer's decision of 2026-10-13: item 58, prebuilt binaries and packages, which the plan had under 0.2.0, ships as 0.1.0's distribution. It changes no Go code.
|
||||
|
||||
Shipped by the maintainer's decision of 2026-10-11 with its ratchet waived: item 182, the shipped data as Go packages, at a632a92. Its last paired ruling against bf1becb was same overall, Mid A better and Junior A worse, with Shape fallen, three seats against the namespace mount in `internal/datafiles/mount.go` and the `at` field of `datafiles.Source`; the scoring run that would rule it worse under the floor was not run. `todo.md` item 197 replaces that mount.
|
||||
|
||||
@@ -966,13 +966,14 @@ data, or the country opens a register.
|
||||
## The apt, dnf and apk repositories are static files on GitHub Pages, holding the latest release only
|
||||
|
||||
2026-10-13, decided by the maintainer. Serves goal 1.1; technical principle: prefer the
|
||||
vendor-neutral option (`~/.claude/principles/technical-principles.md`). A hosted package
|
||||
service would sign and index the packages for us, but only saves tooling, so the repositories
|
||||
are built here: `release-tooling/package-repos.Dockerfile` signs them with a GPG key (apt,
|
||||
dnf) and an RSA key (apk), and any static host can serve the result. GitHub already hosts the
|
||||
code (see "GitHub is canonical"), so Pages adds no new vendor; the image sits on GHCR for the
|
||||
same reason, and as OCI it moves by changing its path. A Pages site holds at most 1 GB and a
|
||||
release's packages take about 35 MB, so the repositories hold the latest release only; every
|
||||
release keeps its own packages, and the image keeps a tag per version. Leaving Pages costs
|
||||
vendor-neutral option (`~/.claude/principles/technical-principles.md`). The repositories
|
||||
are built here, as static files any host can serve: `release-tooling/package-repos.Dockerfile`
|
||||
signs them with a GPG key (apt, dnf) and an RSA key (apk). A hosted package service would
|
||||
only save that tooling. GitHub already hosts the code (see "GitHub is canonical, and the
|
||||
module path names it"), so Pages adds no new vendor. The image sits on GHCR for the same
|
||||
reason; being OCI, it moves to another registry by changing its path. A Pages site holds at
|
||||
most 1 GB and a release's packages take about 35 MB, so the repositories hold the latest
|
||||
release only; each GitHub release still carries its own packages, and the image keeps a tag
|
||||
per version. Leaving Pages costs
|
||||
each Linux user an edit: their apt list, `.repo` file or apk line names `larvit.github.io`.
|
||||
Valid while GitHub hosts the code.
|
||||
|
||||
Reference in New Issue
Block a user