rig's own `ci / check` failed 9 times out of 27 ci.yml tasks on the first Forgejo runner, every one on `shellcheck: command not found`. `ubuntu-latest` maps to catthehacker's SLIM act image, and workflows written for GitHub reasonably assume GitHub's tool surface. Measured before choosing (2026-08-01, streaming ghcr layer blobs rather than pulling): the parity image is 18.67 GB on the wire and 54.52 GB extracted, against a box-class ci tenant with ~34-40 GB free. There is no cheap middle — runner-22.04 is the same slim class, tool for tool, and ships no shellcheck either. `apt-get install -y shellcheck` costs 7s and yields the same ShellCheck 0.8.0 that full-22.04 carries. So the slim default stays and the workflow equips itself. The `command -v` short-circuit keeps either forge from paying for the other; the sudo is a no-op on the act path and load-bearing on GitHub's. `ubuntu-latest-full` ships in the default map beside it: a mapping pulls nothing until a job matches it, and Forgejo freezes labels at registration, so a label absent then cannot be added without re-registering. A plain converge now warns when a runner carries a SUPERSEDED default — matched against the exact strings rig has shipped, so a map the operator chose stays silent. The message says plainly that nothing is broken. Refs #144 |
||
|---|---|---|
| .. | ||
| 109.md | ||
| 111.md | ||
| 112.md | ||
| 116.md | ||
| 129.md | ||
| 131.md | ||
| 133.md | ||
| 135.md | ||
| 144.md | ||
| 152.md | ||
| 153.md | ||
| 160.md | ||
| 162.md | ||
| README.md | ||
changelog.d/ — the next release's section, one fragment per issue
Machine-assembled by bin/changelog-assemble (#112): every PR that changes
behavior writes one file here — <issue>.md, the exact prose that will be
published, nothing else — and the release PR folds them all into the next
## X.Y.Z — DATE section of CHANGELOG.md, consuming them. Distinct
filenames never conflict, which is this directory's whole reason to exist.
This README is the marker that keeps the directory tracked when it holds no
fragments (#112 D1) — changelog-armed refuses a tree without it; do not
delete it.