-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add a special "stable" version identifier that accepts any stable version #36
Comments
cc @munificent wdyt? |
This should only happen if there are no stable versions. Since all pre-release versions are lower priority than all stable versions, an Is there something else going on here? |
There are stable versions, in the |
You can repro by creating a pubspec with |
Note that the pub site properly recognizes it as a pre-release version https://pub.dartlang.org/packages/build_web_compilers |
also cc @natebosch |
Ok, I got some more information here. It looks like if you have only a dependency on The easiest way I have discovered to do that is by adding a dependency on the For this example my pubspec looks like this:
Here is a gist with the output of Note that it lists test first (even though it appears in my pubspec 2nd), and it looks like that is leading to the selection of build_web_compilers 2.0.0-alpha.0? |
Ah, I think this is ultimately because it selects analyzer 0.36 https://gist.github.com/jakemac53/081d8f600e0a569c4821c765b65cd506, which we don't support in older build_web_compilers. |
Today the
any
identifier allows any version (stable or pre-release). Changing that behavior would be a breaking change, hence the proposal for a newstable
identifier.As a concrete use case we advise consumers of the
build_*
packages to generally useany
constraints, because they don't directly interact with the imperative api of the packages. However, we released an2.0.0-alpha.0
version ofbuild_web_compilers
and now they are picking that version up by default, which we expected users to have to explicitly opt into.The text was updated successfully, but these errors were encountered: