The core goes first
Twenty-three adapters went out against a core that had already moved on, and they all needed releasing again. So now something checks the engine's coupled on before the carriages leave.


Twenty-three adapters went out against a core that had already moved on, and they all needed releasing again. So now something checks the engine's coupled on before the carriages leave.

For a week in July the whole estate's CI ran through three slots on one homelab VM, while a fleet of agents worked through twenty-one findings at once.

The runner fleet cost $270 I didn't have, so it went off. The tests stayed on, and the savings came from everything I'd been paying for twice.

I went looking for reproducible CI images and found the builder had been archived fourteen months earlier. Swapping it out turned out to be the easy part.

colophon works out the version your commits have earned, opens the release as a merge request, and tags what actually landed. Not what your forge says did.

The documented cargo cache key gives every lockfile its own cache. On a self-hosted runner that fills the disk. Whose disk was the advice for?

I run a coding session per repository and they can't talk to each other. For a while the thing carrying messages between them was me, and I kept getting it wrong.

Half my CI jobs ran for no reason on every merge request. Skipping them with rules:changes, and why that is trickier than the manual suggests.

Moving off tag-on-merge releases, where a release is a side effect of merging, to a model where the release is itself a reviewable change.

A CI component gated on the default branch fired on every Renovate schedule too, because a scheduled run is also on the default branch.
