Dependency Upgrade Gauntlet: Patch a Critical Library Without Breaking Users

A security advisory lands for a library that sits deep in the stack. The lazy response is panic; the professional response is evidence. Participants inspect the advisory, read the changelog, identify affected paths, run targeted tests, create a canary plan, and decide what rollback looks like.

The session turns dependency updates from background chores into an engineering discipline. It is especially useful for teams with old packages, fragile tests, or fear around touching foundation code.