Use case

It is inevitable that changes to the framework will break builds created with a different release,
When this behavior is observed in beta the fixes are pushed in main
which is totally fine since a choosing a non stable version obviously imply less "stability".
eg: issue identified in beta, fix pushed to main, all good

I believe a developer upgrading the stable release should be warned not only about "breaking changes",
but also if an app created with the previous stable will break using the new stable.

At the moment this doesn't happen
eg: apparently the same issue above made it to stable and the fix is currently cherrypicked

Proposal

I propose to add an automated integration test for all platforms with stable support
that:

1. build the starter app with the previous stable
2. upgrade the flutter version
3. run the app

if the issue is not fixable without developer's action
detect a mismatch "build version" and "run version"
and trigger a warning for the known issue providing a workaround/fix