Unblock a dependency upgrade that broke the build

A dependency upgrade broke my build. Upgrade: {{package, from version, to version}}. Errors: {{paste the first and last 30 lines of the failure}}. Lockfile or manifest: {{paste relevant section}}.

Work it in this order:
1. Read the errors and say what actually failed: a removed or renamed API, a changed default, a peer or transitive version conflict, a build-toolchain or runtime requirement, or a type-only break. Quote the line that tells you.
2. If it is a transitive conflict, show the conflicting range and which package pins it.
3. Give the smallest fix that keeps the upgrade, with the exact code or config diff.
4. Give the fallback if the smallest fix fails: pin, override, patch, or stay behind - and the cost of each.
5. Name what else in my code is likely to break at runtime rather than at build time, and what to test before merging.

Do not tell me to delete the lockfile, clear caches, or upgrade everything else. Do not invent release notes - if the break depends on changelog detail you do not have, say which version's notes I need to read.