-
Notifications
You must be signed in to change notification settings - Fork 30
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
Handle registrying things that don't support the version of julia that the CI is running #430
Comments
A extra challenging case is if a package says it supports say julia |
I don't think we should auto-pass, necessarily. Probably the best thing to do is to figure out what Julia version is needed, and run |
I agree that is the best thing. |
Sadly, Pkg does not throw a rich exception type that we can just read the information from
Maybe as a basic good enough approach we could just check |
Right now Automerge runs julika 1.6
If you register a package release that only supporst say 1.0 or 1.7
then it will fail with
E.g JuliaRegistries/General#42120
The ideal thing to do would be to make sure the CI was running the right version.
Probably an OK thing to do would be to just auto-pass those tests.
It is unusual for someone not to support the current release of julia
and anyone who does probably knows what they are doing.
The text was updated successfully, but these errors were encountered: