← Writing

October 2026

Who owns the patch decision?

'Black October' cost me half a day on a few small apps. Very little of that time went on running commands.

When the advisories started landing last week, my inbox filled with 'urgent' patch emails from OCI, GCP and nearly every other platform my apps touch. I've managed tech stacks for years, and it still rattled me.

Most of the half day went on decisions. Node shipped security releases for 24 and 26, and I was on 25. npm had its own security release taking it to 12, but Node 26 came bundled with 11. In parallel, an n8n MCP update was causing issues with Postgres 17, which meant moving to 18 with a migration script of its own because of a breaking change to the data directory.

I started asking Claude Code questions. What is the support period for Node 24, 25 and 26, and how do their dependencies link up? What is the impact of pairing npm 12 with Node 26 when it ships with 11? Then I had it run a full check across every other component, which flagged sharp as a likely break that needed special handling.

Claude Code answered all of it well, but only because I asked. When it came to the actual choice between 24 and 26, it left it to me without properly giving reasons for either. I went to 26.

The DevOps people in my teams over the years wouldn't wait for my questions. They would have a standing view on which runtime lines we are running and what tends to break when we move. More importantly, the decision would be theirs to make and defend.

Microsoft alone shipped fixes for over 1,400 vulnerabilities in its October Patch Tuesday. Each advisory across a stack needs someone to decide whether it applies and what it might break. I'd guess plenty of teams now run a lot of their DevOps / DevSecOps through coding assistants, and on a normal week that probably holds up. In a month like this one, it gets precarious. If a few small apps took me half a day, knowing what to ask, I suspect it takes a lot longer for a team where nobody is asking.

Vibe-coding teams are in a harder spot. Most don't have anyone designated as DevOps at all. Coding assistants do what they are told, and nobody is telling them to check a support calendar.

If you run a team that ships with coding assistants, look at how your current runtime version was chosen. If the honest answer is 'the assistant suggested it', then nobody chose it.

Who on your team owns that call today?

#DevSecOps #VibeCoding #AIGovernance

React to this post

Comments