-
Notifications
You must be signed in to change notification settings - Fork 94
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
Inconsistent dependency on ArnoldiMethod #354
Comments
The PR fixing it has been waiting for a review, if you review it I can merge and tag a release |
The current (from #344) version again seems to fix the version of ArnoldiMethod.jl (thanks!), but we will also need to increase the version number of this package (e.g. to 1.9.1) (otherwise, there will still be problems). On the use of ArnolidMethod.jl: |
Yeah I know we need to tag a new release, I'm just waiting to merge one or two more PRs first. This will happen next week at the latest |
Do you need a new release urgently? Otherwise you also specify that you want use |
Thanks. I do need a new release (an internal project has a direct dependency on ArnoldiMethod.jl, and a transitive dependency on Graphs -- so, it does not seem possible to just |
@simonschoelly there's no problem with releasing often, right? Since we have adopted ColPrac, the standard could even be to release after each PR |
This is resolved with the package registration from last week, right? |
Yes indeed, let's close |
The Project.toml for the project in v.1.9 restricts ArnoldiMethod to v0.3 (
ArnoldiMethod = "0.3"
). However, in the official package repository (https://juliahub.com/ui/Packages/General/Graphs), the compatibility constraint is for v1.0 or v2.0 (ArnoldiMethod = "0.1, 0.2").As a result, using the package still restricts ArnoldiMethod to v0.1 or v0.2.
It seems that the dependency has been updated but without updating this packages version number and without pushing the change to the official repo.
Would it be possible to fix this please?
The text was updated successfully, but these errors were encountered: