SDK and framework migrations

A model API is a wire format and it changes slowly. The libraries wrapped around it are software, and they change at the speed of software. Almost nothing in this cluster is about a model behaving differently; it is about a client library that renamed a class, split itself into four packages, or replaced a constructor with a factory function, and about the specific hour you spend afterwards reading tracebacks that point at your own code.

These pages take one named jump each and walk the call sites. They quote the error the upgraded library actually raises, because that string is usually the only evidence you have, and they are explicit about the part of a migration nobody writes down: what has no equivalent on the other side, and what you do instead. Where a page names a version, treat the version as part of the claim — run the command that prints what you have installed before trusting a mapping table, including this one.