The advisory

Wednesday, 8:12 a.m. A security advisory is published for a library Traversal depends on, three days into a freeze whose entire point was that nothing would change.

The advisory is public, which means every attacker on earth just received it too. A fix exists: the maintainers have shipped 4.2.2, a patch release in exactly the sense Act II taught, one problem, compatible, take it now. And taking it means deploying to production during the freeze, which is how Priya and Finn end up in a small room deciding between two risks instead of between a risk and a rule.

The way back, designed first

What makes the decision survivable is that modern delivery keeps an undo button. Redeploying the previous known-good version is a rollbackConcept · lights on your maprollbackRedeploying the previous known-good artifact: undoing a bad deploy by returning to what worked. Fast and routine when artifacts are versioned, with one deep caveat: code rolls back easily, and already-written data does not., and the team writes the rollback plan before touching anything, which is the discipline in one sentence. Decide how you will retreat, then advance.

The patch itself rides as a hotfixConcept · lights on your maphotfixA minimal, urgent fix rushed through the pipeline ahead of normal work: the smallest possible change, full tests still run, deployed immediately. The delivery system’s fire lane. Same road, sirens on, no gates skipped.: the smallest possible change, sirens on, every gate still passed. Two reviewers read the tiny diff before eleven; the nightly fake marathon runs against it at noon. A canary takes it first, five percent, watched. By 3:40 the patched library is everywhere, the freeze is intact in spirit, and nothing anywhere looks different, which was the entire ambition.

Why it could be done at all

The quiet hero is a promise the maintainers kept: backward compatibilityConcept · lights on your mapbackward compatibilityNew versions continuing to work with what already exists: old clients, old data, old integrations. The constraint that makes gradual rollouts and rollbacks possible at all, since during any deploy, old and new briefly coexist and must understand each other.. 4.2.2 behaves exactly like 4.2.1 minus one hole, so Traversal could swap it mid-freeze without touching anything else. The opposite kind of change, one that old callers cannot survive, is a breaking changeConcept · lights on your mapbreaking changeA change that existing clients, data, or integrations cannot survive: renamed fields, dropped endpoints, incompatible shapes. Sometimes necessary, never casual, and the reason major version numbers and long deprecation countdowns exist., and it is why the first digit of a version number gets its own ceremony. Nobody ships one of those during a freeze. Nobody sane ships one the week before a marathon.

The advisory itself came from the world’s ongoing habit of security testingConcept · lights on your mapsecurity testingProbing systems for vulnerabilities before attackers find them: automated scans, dependency audits, and hired professionals attempting real break-ins. The discipline that produces advisories like this one., somebody, somewhere, probing the library the way attackers would and publishing what they found. The full anatomy of what they look for is an Act IV story, and the audit there will remember this Wednesday kindly.

Rules exist to serve outcomes. The team broke the freeze to honour what the freeze was for, wrote down why, and went to lunch late. That night, Sam breaks something much bigger, on purpose.