My fix for a data-loss bug sat in a green PR for four days. Every install in that window still had the bug.

Short summary

A solo open-source maintainer discovered their data-loss bug fix sat in a green PR for four days because merging was only the first step of a five-step manual release ritual. The automated parts—CI tests, packaging checks—held perfectly, while every manual step (merge decision, changelog entry, release cutting) silently drifted. The insight: machine-watched processes are reliable; human-only processes decay silently and consistently.

• •A correct, CI-green bug fix sat unmerged for four days due to manual release ritual friction
• •Automated pipeline steps held; every manual-only step (changelog, merge decision, release) silently drifted
• •Core lesson: machine-watched shipping steps are reliable, human-only steps decay in the same direction every time

Generated with AI, which can make mistakes.