Every deprecated-runtime migration produces the same shape of pain: you bump one version number, redeploy, and get hit with errors that look unrelated to each other but are all downstream of the same jump. The errors aren't random — for a given upgrade path, they show up in a fairly predictable order. This is a map, not a new deep dive. Each line below is a real, verbatim error with its own fix already written up — this just sequences them by which upgrade produces them , so you know what's ...