Plan an SDK upgrade
Keep version changes explicit and preserve operating intent when an integration changes.
Source 0.1.0 Private source package
No public version migration yet
There is no migration between published SDK releases to apply. Do not treat a source checkpoint as a drop-in supported upgrade. Compare its source contracts and run your own integration checks in an isolated environment.
What future migration guides will include
A migration will name its source and destination releases, changed contracts, tested before/after examples and required operator decisions. Deprecated methods will link to replacements. Upgrading must never restore stale authority or replay saved movement input.