v1.2 release and migration readiness¶
Problem¶
The v1.2 release will introduce breaking changes to template YAML schema, rendering behavior, or query conventions that affect published templates in the catalog. There is no migration plan, no upgrade guidance for users who forked existing templates, and no communication strategy to set expectations. Without release readiness preparation, the upgrade will break existing user dashboards silently and generate a wave of support requests that could have been prevented with proactive guidance.
Context¶
Possible Solutions¶
Plan¶
Implementation Progress¶
Review Feedback¶
- Review cleared