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
[>= 4.1.0-dev+1] Unavailable on stable #379
Comments
That version constraint is here because it is needed. This version relies on a recent change made on Flutter. I could technically remove the feature related to these change, but that would make introducing it later a breaking change. I prefer to keep 4.1.0 a dev release than having a 5.0.0 already. |
@rrousselGit Will useful features like |
Well, if you are fine with using the dev version of provider, why don't you use a different flutter channel that is up to date? |
I use 4.1.0 because I confirmed it works fine and I know your work is trustworthy. Even if some bug was found, it is expected that you rapidly deal with it. On the other hand, Flutter's non-stable channels have so many commits added frequently that it is virtually impossible to track all of them. However, I'm thinking the dev channel may be fairly fine, which does not have 1.15.17-pre.5 yet though. |
4.1.0-dev should work fine. But if there's a bug, you'll get stuck as I don't plan to support both with and without the Flutter changes together. It's your call |
OK. That's what I wanted to know. If it's not supported, I'll choose a different version with more support. Thanks. IMHO, I think it would be better if it was documented somewhere. |
I mean it was one of the two things I wanted to know. How about the other one?
|
No, that would be against semver, and it depends on the |
I can decide on the version I should use now. Thank you for all the info. |
downgrading from provider: ^4.1.3 to provider: ^3.1.0 fixed my problem |
Why did you need that? |
4.1.0 didnt work either
…On Thu, Jun 25, 2020, 16:16 Remi Rousselet ***@***.***> wrote:
Why did you need that?
4.1.x is compatible with stable.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#379 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJTUIC74RKQTPBAEZAUZD7TRYNS4PANCNFSM4LEYOX6A>
.
|
Are you sure you didn't forget to update flutter? |
am using Flutter version 1.12, which is compatible with 3.1.0, 4.1.0
requires flutter version 1.15
…On Thu, Jun 25, 2020, 16:36 Remi Rousselet ***@***.***> wrote:
Are you sure you didn't forget to update flutter?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#379 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJTUIC2KSS54BVRXWRO3MZ3RYNVJVANCNFSM4LEYOX6A>
.
|
Flutter stable is currently on 1.17 |
okay
I have to update my packages, and flutter version
…On Thu, Jun 25, 2020, 16:56 Remi Rousselet ***@***.***> wrote:
Flutter stable is currently on 1.17
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#379 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJTUIC2DGOLMO34RUHDQHELRYNXUFANCNFSM4LEYOX6A>
.
|
I noticed newer versions of provider were up and decided to update from v4.1.0-dev to v4.1.0-dev+2 today, but
pub get
failed on thestable
channel.Is
flutter: '>= 1.15.17-pre.5'
in pubspec.yaml of provider not going to be removed until Flutter 1.15.17-pre.5 comes to stable, or is it just a temporary measure only during the pre-release phase of 4.x?It is expected to take months before 1.15.17-pre.5 arrives in the stable channel. It'll be inconvenient for users if newer provider versions are not available for such a long time while attractive features are newly added in 4.x.
The text was updated successfully, but these errors were encountered: