Re-enable downgrade CI#600
Merged
ChrisRackauckas merged 1 commit intoMay 31, 2026
Merged
Conversation
The Downgrade workflow was disabled (`if: false`) due to issue SciML#522 (a JET test dependency incompatible with downgrade). The downgrade job only runs the Core test group, which never loads JET (JET is exercised solely in the `nopre` group via test/jet_tests.jl), so the JET incompatibility does not affect this job. The julia-actions/julia-downgrade-compat tooling problems that affected SciML monorepos are fixed and released in `@v2`. Re-enable the job and set `allow_reresolve: true` on the runtest step so the test environment can resolve transitive/test-only dependencies the downgrade step does not lock (the main env stays pinned to the minimal compatible versions, which is what the downgrade test checks). Also raise a few compat lower bounds to the true minimal mutually-consistent values (respecting the bundled lib/ path deps), all already-released versions: - RecursiveArrayTools: ArrayInterface 7.16 -> 7.17, Tables 1.12 -> 1.12.1 - RecursiveArrayToolsRaggedArrays: ArrayInterface 7 -> 7.17, StaticArraysCore 1.4 -> 1.4.2, SymbolicIndexingInterface 0.3.35 -> 0.3.42 Verified locally on Julia 1.11: downgrade resolve + build + Pkg.test(allow_reresolve=true) pass for the main package (Core) and for all three lib/ subpackages. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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.
Please ignore until reviewed by @ChrisRackauckas. Draft.
Re-enables the
Downgradeworkflow, which was disabled withif: falseper issue #522 (a JET test dependency incompatible with downgrade).Why this is safe: the downgrade job only runs the
Coretest group. JET is exercised solely in thenopregroup (test/jet_tests.jl, gated byGROUP == "nopre"), so the Core downgrade job never loads JET and the #522 incompatibility does not apply here. The julia-actions/julia-downgrade-compat tooling problems that affected SciML monorepos are fixed and released in@v2.Changes:
if: false.allow_reresolve: trueon the runtest step (the released minimal manifest restores path deps but not their full transitive closure; allow_reresolve lets the test env fill that in while the main env stays pinned to minimal versions).Verified locally on Julia 1.11 (each project in its own depot): downgrade resolve + build +
Pkg.test(allow_reresolve=true)all pass for the main package (Core group) and for all three lib/ subpackages (ArrayPartitionAnyAll, RaggedArrays, ShorthandConstructors). Nojulia =compat entries were changed.🤖 Generated with Claude Code