Migration Notes
Migration notes collect version-to-version upgrade guidance for Rogue and PyRogue. Use them when an existing application or Device library needs to move forward across a release boundary and you want to identify behavioral changes, removed APIs, and the newer patterns that replace them.
Migration notes are intentionally narrower than the main narrative documentation. The rest of the manual explains how the current APIs and workflows are intended to be used. This section focuses on what changed and what older code needs to be updated.
In practice, a migration pass usually involves:
Identifying features that moved to a different subsystem or interface model,
Updating construction and lifecycle patterns,
Replacing removed APIs with the supported equivalents,
Then returning to the main section docs for the current recommended design.
Not every release needs a migration note. These pages are only added when a version introduces changes that are significant enough to affect existing applications.
What To Explore Next
Migrating To Rogue V6 for the major interface and API transitions introduced in Rogue V6
API Reference
Migration: