Library major-version upgrades
Suitable when the scope and expected result can be made explicit before implementation.
Dependency Upgrade
Move the dependencies forward without dragging the whole roadmap with them.
We baseline the current build, define the exact package/version target, update the dependency set, repair required compatibility issues, rerun tests, and separately review the diff.
Good fit
Bounded work with a visible finish line.
Security-driven package updates
Suitable when the scope and expected result can be made explicit before implementation.
Lockfile and compatibility refreshes
Suitable when the scope and expected result can be made explicit before implementation.
SDK replacement within one integration
Suitable when the scope and expected result can be made explicit before implementation.
Read-only preflight
What we verify first.
Preflight gathers evidence. It does not authorize implementation.
Current and target package versions
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Manifest / lockfile evidence
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Existing build and test path
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Required compatibility work vs optional cleanup
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Lane use
Implementation stays inside the approved brief.
The implementation lane is allowed to make compatibility changes required by the approved target. Optional refactors, broad modernization, and unrelated package churn remain out of scope.
Definition of done
Evidence before handoff.
The approved dependency target is reached, required compatibility changes are complete, and the agreed build/test evidence passes.
Client controls merge. Deploy remains off by default.