Bump sublibrary/test Corleone compat 0.0.4 -> 0.0.5 to match released parent#106
Merged
ChrisRackauckas merged 1 commit intoJun 28, 2026
Conversation
… parent PRs SciML#104/SciML#105 released parent Corleone v0.0.5 but did not update the sublibraries' / test sub-projects' Corleone [compat], which still pinned "0.0.4". For pre-1.0 versions the caret range "0.0.4" means [0.0.4, 0.0.5), so the path-sourced parent at 0.0.5 ([sources] Corleone = {path = "../.."}) has an empty intersection with that compat. The downgrade-sublibraries lanes (lib/CorleoneOED, lib/OptimalControlBenchmarks) — and the regular Sublibrary CI / QA lanes — fail during the test-sandbox resolve with: ERROR: LoadError: empty intersection between Corleone@0.0.5 and project compatibility 0.0.4 The downgrade root (main) lane is unaffected because the root package does not depend on itself. This mirrors PR SciML#101 (the same 0.0.3 -> 0.0.4 bump after the v0.0.4 parent release). Also bumps the now-stale CorleoneOED self-compat (0.0.4 -> 0.0.5) in lib/CorleoneOED/test/qa/Project.toml, since CorleoneOED was released as v0.0.5 (SciML#105) and is path-sourced there. OptimalControlBenchmarks stays at 0.0.3 (matches its current version). Verified locally on Julia 1.10.11 (lts): Pkg.develop of the path-sourced parent throws the empty-intersection error on the unmodified tree and succeeds (Corleone v0.0.5 accepted) with this change. Ignore until reviewed by @ChrisRackauckas. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
ChrisRackauckas-Claude
pushed a commit
to ChrisRackauckas-Claude/Corleone.jl
that referenced
this pull request
Jul 3, 2026
Brings in the released parent bumps (v0.0.5, SciML#104/SciML#105) and the Corleone/CorleoneOED compat 0.0.4 -> 0.0.5 bump (SciML#106). The stale Corleone = "0.0.4" pin in the three QA-env Project.toml files was causing every QA lane to fail at Pkg resolution with "empty intersection between Corleone@0.0.5 and project compatibility 0.0.4" before any Aqua/ExplicitImports check ran. The run_qa conversion (qa.jl) and the SciMLTesting = "1.6" pins are preserved unchanged. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
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.
Problem
The Downgrade Sublibraries lane (and the regular Sublibrary CI / QA lanes) are red on
main:PRs #104/#105 released parent Corleone v0.0.5 but did not update the sublibraries' / test sub-projects'
Corleone[compat], which still pinned"0.0.4". For pre-1.0 versions the caret range"0.0.4"means[0.0.4, 0.0.5), so the path-sourced parent at 0.0.5 ([sources] Corleone = {path = "../.."}) has an empty intersection with that compat. The conflict surfaces during thePkg.testtest-sandbox resolve.The root Downgrade (main) lane is green because the root package does not depend on itself.
This is the same recurring pattern that PR #101 fixed for the
0.0.3 -> 0.0.4parent release.Fix
Bump
Corleone = "0.0.4"->"0.0.5"in the 5 path-sourcing Project.tomls, plus the now-staleCorleoneOED = "0.0.4"->"0.0.5"self-compat inlib/CorleoneOED/test/qa/Project.toml(CorleoneOED was released as v0.0.5 in #105 and is path-sourced there).OptimalControlBenchmarksstays at0.0.3(matches its current version).Files:
lib/CorleoneOED/Project.tomllib/CorleoneOED/test/qa/Project.toml(Corleone + CorleoneOED)lib/OptimalControlBenchmarks/Project.tomllib/OptimalControlBenchmarks/test/qa/Project.tomltest/examples/Project.tomltest/qa/Project.tomlVerification (Julia 1.10.11, lts)
Pkg.developof the path-sourced parent intolib/OptimalControlBenchmarks:empty intersection between Corleone@0.0.5 and project compatibility 0.0.4(reproduces the CI error byte-for-byte)Corleone v0.0.5 ../..acceptedAlso confirmed via
semver_spec:0.0.5 ∈ "0.0.4"isfalse(the conflict),0.0.5 ∈ "0.0.5"istrue(the fix).Note: a clean-depot full
Pkg.testresolve still hits the separate, pre-existing fleet-wide LogExpFunctions/SparseConnectivityTracer upstream resolution wall; that is independent of this compat bump and is not what these lanes were failing on (they died earlier, at the Corleone compat check).Ignore until reviewed by @ChrisRackauckas.
🤖 Generated with Claude Code