-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please be more careful when upgrading - Build break from flare_flutter #208
Comments
Hi @yjoo9317, sorry to hear about that. I think I see what happened. We revved the SDK as the library was already using features that were in the newer SDK which we weren't properly depending on in the pubspec. The right thing to do there would've been to combine that change with a major version change, which is unfortunate but I think necessary. Let me know if you have further recommendations, we definitely don't want to break builds. Sorry about that, we'll be more careful in the future. |
Thanks @luigi-rosso for quick response. |
@luigi-rosso @yjoo9317 Thanks for the insight. Very timely for us! What's the recommended workaround, please? Our
But
|
@thetanz-geoff |
Thanks for the speedy reply, @yjoo9317. |
Hi @luigi-rosso
We'd been using flare 1.6.5 since we couldn't update flutter SDK to the latest for internal reasons and suddenly we got a build break a week ago.
Apparently, the recent flare_dart upgrade (to 2.3.?, I guess) was causing the break as our build system starts fresh builds.
Since the flare spec points to flare_dart ^2.2.X and our build system picked flare_dart 2.3.0 which requires additional interface implementation for actor class.
If flare_dart upgrade can cause the build break, then it should be carefully delivered to avoid any possible breakage for existing flare versions.
Thanks.
The text was updated successfully, but these errors were encountered: