Migration Guides
Major Monster releases may make contracts stricter when the old behavior could hide broken components. These guides describe the observable change, the required consumer migration and the checks to run before upgrading.
How to use a migration guide
- Search your subclasses for every removed or tightened pattern.
- Move code to the lifecycle phase that owns the state it needs.
- Run construction, connection and reconnect tests before changing the dependency range.
- Review component-specific release notes for unrelated changes in the same major release.