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.

I sent the bouncer home so a Go test could get in. It turned out he'd been turning away malware since the summer, and he wouldn't come back.

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.

A release token showed up in use from four machines in AWS that I couldn't account for. Two hours later it turned out to be my own runner fleet, and I'd fixed the real problem anyway.

A plugin marketplace has no registry, so whatever's on main is what people install. I tried twice to get CI to keep the version honest before settling for a check that makes me type a command.

Forty-two comments telling a checker to stand down. I went through them one at a time to see what each was actually asserting, and some of them were wrong.

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.

The homelab finally ran out. Not disk this time, capacity. So the overflow went to AWS, on the condition that it costs nothing when nobody's pushing.

An hour to compile and 170GB of artefacts to clean up afterwards. Rust has a built-in answer to that, and I only used half of it.

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.
