Our ideal fix for any serious issue is to create a “hotfix” release by taking an existing release and “cherry picking” the fixes that we’d like to apply. The ability to hotfix an existing stable release is something that we implemented for 1.2 but have not quite gotten to production quality. The consequence of this is that if we had created a new stable “1.2.1-a” release with the fix for the regressions, we’d have stranded all of our users at that branch; updating to future branches would’ve required users to remove and reinstall Flutter from scratch, which was clearly unacceptable. We are working hard to validate our ability to hotfix in 1.3+ so that we don’t have this problem again.