Prep for v1.46.0

[odow]

Basic

• version field of Project.toml has been updated
  - If a breaking change, increment the MAJOR field and reset others to 0
  - If adding new features, increment the MINOR field and reset PATCH to 0
  - If adding bug fixes or documentation changes, increment the PATCH field

Documentation

• Add a new entry to docs/src/changelog.md, following existing style

Tests

• https://github.com/jump-dev/MathOptInterface.jl/actions/runs/18326452732
• https://github.com/jump-dev/MathOptInterface.jl/actions/runs/18362251645
• https://github.com/jump-dev/MathOptInterface.jl/actions/runs/18511698884
• If new tests were added, ensure that MOI.Test.version_added is implemented.

[odow]

The Juniper and Pavito failures are super interesting and they are caused by #2857

• They have z --> {f(x) in S}, z in {0, 1}
• They have an outer solver that covers z in {0, 1}. They pass z --> {f(x) in S}, z == a to the inner solver. The inner solver says, sure, I know how to reformulate --> assuming z is binary. But z is fixed and isn't {0, 1}. The reformulation is still valid though, which is why the tests were passing before.

Maybe we should revert #2857 and add a check at the JuMP level?

Or maybe the bridge needs to say: I added a ZeroOne constraint even though I didn't just so we validate that an indicator can't be bridged by a continuous solver.

Or maybe we need to convert the error() AddConstraintNotAllowed.

[odow]

https://github.com/jump-dev/MathOptInterface.jl/actions/runs/18362251645

[odow]

• BARON: emailed Nick
• DSDP: Test failures DSDP.jl#45
• PolyJuMP: known
• SDPA: [SDPA] update to v7.3.19 JuliaPackaging/Yggdrasil#12251
• SumOfSquares: known
• BlockDecomposition: Repo status realopt/BlockDecomposition.jl#9
• Coluna: Repo status realopt/BlockDecomposition.jl#9
• EAGO: some generated function/Cassette thing
• FrankWolfe: Refactor test files into modules ZIB-IOL/FrankWolfe.jl#621
• SetProg: Does not compile on Julia 1.12 kalmarek/SymbolicWedderburn.jl#97

[odow]

Hearing no objections?

[blegat]

The Juniper and Pavito failures are super interesting and they are caused by #2857

* They have `z --> {f(x) in S}, z in {0, 1}`

* They have an outer solver that covers `z in {0, 1}`. They pass `z --> {f(x) in S}, z == a` to the inner solver. The inner solver says, sure, I know how to reformulate `-->` assuming `z` is binary. But `z` is fixed and isn't `{0, 1}`. The reformulation is still valid though, which is why the tests were passing before.

Maybe we should revert #2857 and add a check at the JuMP level?

Or maybe the bridge needs to say: I added a ZeroOne constraint even though I didn't just so we validate that an indicator can't be bridged by a continuous solver.

Or maybe we need to convert the error() AddConstraintNotAllowed.

Pavito and Juniper shouldn't support Indicator constraints so that it's bridged before they pass it down. It doesn't make sense for them to pass down an indicator constraints to a non-MIP solver. It's not like there is a chance for these non-MIP solvers to support indicator constraints.

[blegat]

Maybe this should be fixed before we release ?

[odow]

Already done in #2868