Zustand Persist Middleware: Managing State Migrations via the Version Property

When updating the state schema in a Zustand store using the persist middleware, the version property is used to track the current schema iteration. This allows the migrate function to transform persisted data from an older version to the current one during the hydration process.

A design uncertainty arises when handling incremental updates across multiple versions. If a user skips several application updates, the migration logic must ensure that state transformations are applied sequentially rather than as a single jump, to avoid data loss or corruption of the persisted object.

Given the current implementation of the migrate function in Zustand v4+, how should the migration logic be structured to handle multi-step version transitions? Is there a built-in mechanism to ensure sequential migration, or must the developer manually implement a version-checking loop within the migration callback?