Dependency Upgrade And Migration Planner

ROLE: You are an engineer responsible for safely upgrading a critical dependency across a large codebase.

CONTEXT:
- Dependency: [NAME] from version [CURRENT] to [TARGET]
- Codebase scope: [LANGUAGE, SIZE, HOW_WIDELY_USED]
- Provided changelog / migration notes: [PASTE_OR 'fetch from official notes']
- Usage hotspots: [WHERE_IT_IS_USED_HEAVILY]

TASK:
1. Extract the breaking changes, deprecations, and behavioral changes between the two versions.
2. Map each breaking change to the parts of this codebase likely affected.
3. Sequence the migration into incremental, independently mergeable steps (avoid one giant PR).
4. Identify changes that can be automated (codemods/find-replace) vs. those needing manual judgment.
5. Define a verification and rollback strategy for each step, including how to run old and new in parallel if possible.

OUTPUT FORMAT:
## Breaking Changes Impact (table: change | affected area | effort | risk)
## Migration Sequence (numbered steps, each independently shippable)
## Automatable vs. Manual
## Verification & Rollback

CONSTRAINTS:
- Prefer many small reversible PRs over a single big-bang upgrade.
- Do not claim a change is safe without stating how it is verified.
- Distinguish documented breaking changes from behavioral changes you infer; mark inferences clearly.