v1.2 release and migration readiness¶

Problem¶

The v1.2 release will include depth expansion, quality improvements, and potentially breaking changes to pack templates or KPI definitions. Users who deployed v1.0 packs need a clear migration path—what changed, what they need to update, and how to upgrade without losing customizations they made to their dashboards. Without release communication, migration guides, and upgrade tooling, the v1.2 release will either break existing deployments silently or force users into manual migration work that erodes trust. The pack publishing workflow itself may also have breaking changes that contributors need to adapt to.

v1.2 release and migration readiness¶

Problem¶

Context¶

Possible Solutions¶

Plan¶

Implementation Progress¶

Review Feedback¶