Compatibility bottlenecks in the MLJ Model Registry

There are are few packages in the registry whose compatibility updates may block use with other models the registry. This is an edited list of the output of ] status --outdated -m for the model registry after an update today. I have omitted .jll packages. The most concerning are packages not updating to latest Optim.

Be great if we could get help chasing some of these down.

• ⌅ [7317a516] DynamicDiff v0.2.1 (<v0.3.1): SymbolicRegression
• ⌅ [a40a106e] DynamicExpressions v1.10.4 (<v2.5.2): DynamicDiff, SymbolicRegression
• ⌃ [d3d80556] LineSearches v7.5.1 (<v7.6.0)
• ⌅ [d41bc354] NLSolversBase v7.10.0 (<v8.0.0): LineSearches, Optim
• ⌅ [429524aa] Optim v1.13.3 (<v2.0.1): MLJLinearModels, SymbolicRegression
• ⌅ [92933f4c] ProgressMeter v1.10.2 (<v1.11.0): SymbolicRegression
• ⌅ [68821587] Arpack_jll v3.5.2+0 (<v3.9.2+0): Arpack

The maintainer of SymbolicRegression is aware of the issues here; v 2.0 of that package aims to resolve these.

Start with the edited ] status --outdated -m output in this issue and investigate the listed packages, especially the compatibility paths involving Optim, LineSearches, NLSolversBase, and SymbolicRegression. Check whether the outdated constraints can be resolved or whether they are blocked by the planned SymbolicRegression v2 work; done means the registry no longer has the identified blocking incompatibilities or the remaining blockers are documented.