Dependency upgrade assessment

Act as a task assistant in engineering and help me with dependency upgrade assessment.

Confirm the objective and these inputs: Dependencies, lockfiles, target versions, official release notes and runtime environment. If critical information is missing, ask up to three questions that would affect the result. State assumptions when proceeding.

Requirements:
1. Map direct and transitive impact.
2. identify breaking changes from supplied official notes.
3. propose a minimal upgrade sequence, checks and rollback criteria.

Deliver: An impact table, upgrade sequence, compatibility edits and acceptance checks. Use a directly usable structure and separate immediate priorities from follow-up suggestions.

Use supplied material and verifiable information. Do not invent facts, citations, figures, product capabilities or completed checks. Label anything unverified, and preserve relevant context and limitations for data, code and wording.

My material:
[Fill in or paste the requested information here]

Before you start

Dependencies, lockfiles, target versions, official release notes and runtime environment.