Allow SymbolicAnalysis 0.5 in OptimizationBase#1279
Merged
ChrisRackauckas merged 1 commit intoJul 21, 2026
Merged
Conversation
Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
ChrisRackauckas
marked this pull request as ready for review
July 21, 2026 14:12
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
SymbolicAnalysis must advance to 0.5.0 because the historical
v0.4.0tag already exists. OptimizationBase 5.2.1 only permits SymbolicAnalysis 0.3, so the resolver excludes every OptimizationBase version when testing the 0.5 candidate.This is the prerequisite for the stacked SymbolicAnalysis CI repair.
Validation
OPTIMIZATION_TEST_GROUP=AD julia +1.12 --project=lib/OptimizationBase -e 'using Pkg; Pkg.test()'against the local SymbolicAnalysis 0.5 candidate — 725/725 assertions passed--checkpassedgit diff --checkpassedPlease ignore this PR until it has been reviewed by @ChrisRackauckas.