v1.2 release and migration readiness¶
Problem¶
The v1.2 release will introduce YAML contract changes that require existing dashboards to be migrated, but there is no established process for communicating breaking changes to users, providing automated migration tooling, or publishing upgrade guides. Without release-and-migration readiness, users will discover breaking changes only when their dashboards fail to compile after upgrading, with no clear path to fix them — leading to support burden and erosion of trust in the upgrade process.
Context¶
Possible Solutions¶
Plan¶
Implementation Progress¶
Review Feedback¶
- Review cleared