-
Notifications
You must be signed in to change notification settings - Fork 365
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
[Opam 2.1.0~beta2] opam upgrades suggests beta variants by default #4404
Comments
New in 2.1 is a package flag It is not yet being used in Thanks for reporting! |
I'm not sure you understood correctly my problem, otherwise I have not understood you. When I do As far as I understand, tagging beta versions of ocaml as hidden would implement a more relaxed (but ok to me) version of what I imagine, but the way it is handled now by opam seems wrong to me. |
I get this message when I do
Can you confirm this is an issue and that it will be fixed with the flag |
Just to be able to do a meaningful example, what’s |
For an easier example, I have another switch for dune only :
|
By default,
opam upgrade
wants to upgradeocaml
to its highest version (4.13.0
as of now), even if this variant is in beta.I think this is not a good idea in general. I don't know about it, but it may be due to the fact tham
opam
itself is in a beta version, but even thenocaml-beta-repository
is not enabled, so I don't think it should be proposed.The text was updated successfully, but these errors were encountered: