v1.2 release and migration readiness¶

Problem¶

The v1.2 release may introduce breaking changes to extension settings, YAML schema expectations, MCP tool contracts, or profiler/inspector panel APIs. Users on v1.0 need a clear upgrade path — what changed, what action they need to take, and whether their existing dashboards will continue to work. Without migration guides, changelog documentation, and in-extension upgrade notifications, users will experience silent breakage after auto-update or will avoid upgrading entirely, fragmenting the user base across versions. Release readiness also requires validating that the upgrade path works across the supported matrix of VS Code versions, OS platforms, and dbt project configurations.

v1.2 release and migration readiness¶

Problem¶

Context¶

Possible Solutions¶

Plan¶

Implementation Progress¶

Review Feedback¶