v1.2 release and migration readiness¶

Problem¶

The v1.2 release will likely introduce changes to the inspect.json schema (new profile fields, restructured distribution data, updated semantic type taxonomy), which means users' existing cached profiles may be incompatible with the new inspector rendering. Without a migration path — schema versioning, automatic upgrade of cached profiles, clear changelogs explaining what changed and why, and rollback guidance if the upgrade causes issues — users will encounter broken inspector reports after upgrading and have no way to resolve the situation short of re-profiling all their tables from scratch. Release migration readiness ensures that the upgrade experience is smooth and users retain trust in their cached data.

v1.2 release and migration readiness¶

Problem¶

Context¶

Possible Solutions¶

Plan¶

Implementation Progress¶

Review Feedback¶