cjdoris / julia-downgrade-compat-action Goto Github PK

Say your compat looks like this:

[compat]
A = "1.5"
B = "2.2"

but package B's compat is

[compat]
A = "1.6"

Does applying this action yield unresolvable package versions?

I think this may be the issue that I'm having here, for A=ForwardDiff and B=SpecialFunctions.

Some Julia packages organize their tests using a Project file in the test folder, e.g.:
https://github.com/SciML/Optimization.jl/blob/master/test/Project.toml
If I understand this action correctly, the additional Project file will not be downgraded.

Similarly, there are sometimes additional Project files in the lib folder, e.g.:
https://github.com/SciML/Optimization.jl/blob/master/lib/OptimizationBBO/Project.toml

I think it would be a useful option to jointly downgraded all these Project files before testing.

How can I get this to work with standard libraries?

For example, I have this in my compat:

Statistics = "1.7"
julia = "1.7"

But I get this error from this action:

ERROR: LoadError: Unsatisfiable requirements detected for package Statistics [10745b16]:
 Statistics [10745b16] log:
 ├─possible versions are: 1.10.0 or uninstalled
 └─restricted to versions 1.7 by RestrictedBoltzmannMachines [12e6b396] — no versions left
   └─RestrictedBoltzmannMachines [12e6b396] log:
     ├─possible versions are: 3.2.7 or uninstalled
     └─RestrictedBoltzmannMachines [12e6b396] is fixed to version 3.2.7-DEV

See https://github.com/cossio/RestrictedBoltzmannMachines.jl/actions/runs/7862238592/job/21451486203.

This action is really helpful. Can I apply the downgrade locally in a branch, in order to to test it before activating the CI on github?

In case, its not locally accessible yet, I suggest to ask ufechner, if it can be implemented at PkgHelpers.jl.

There seems to be general interest in what this does so it seems a good fit for https://github.com/julia-actions