Downgrade Sublibraries CI failing due to upstream compatibility issues

[ChrisRackauckas-Claude]

Description

The Downgrade Sublibraries CI workflow is failing for multiple subpackages due to upstream compatibility issues when testing with downgraded (minimum compatible) package versions.

Affected Packages

1. OptimizationSciPy

Error: PythonCall initialization failure

SystemError: Type does not define the tp_name field.
ERROR: LoadError: InitError: Error initializing 'juliacall.ValueBase'

This appears to be a PythonCall compatibility issue with Julia 1.10.

2. OptimizationOptimJL

Error: LineSearches bounds error

BoundsError: attempt to access Float64 at index [2]
Stacktrace:
  [1] indexed_iterate(I::Float64, i::Int64, state::Nothing)
  [2] (::LineSearches.var"#ϕdϕ#2"{...})
  [3] (::LineSearches.HagerZhang{Float64, Base.RefValue{Bool}})(...)

This is a LineSearches.jl compatibility issue with the barrier optimization in Optim.jl.

3. OptimizationQuadDIRECT

Error: QuadDIRECT algorithm assertion failure

AssertionError: xsplit[1] < xsplit[2] < xsplit[3]

This is an internal QuadDIRECT.jl algorithm error.

4. OptimizationMOI

Same as #1136 - AutoSymbolics + AmplNLWriter NaN issue

Workaround

The Downgrade Sublibraries workflow has been temporarily disabled with if: false to unblock CI.

Re-enablement Criteria

The workflow can be re-enabled once:

1. PythonCall compatibility with Julia 1.10 downgrade is fixed
2. LineSearches/Optim.jl barrier optimization compatibility is resolved
3. QuadDIRECT.jl algorithm issue is addressed

Related Issues

• AutoSymbolics with AmplNLWriter produces NaN results in HS071 test #1136 (AutoSymbolics + AmplNLWriter)

[SebastianM-C]

We should bump the versions to the most recent ones, if the normal CI works, that pretty much means we're incompatible with the old versions due to bugs.