Fix downgrade CI config (julia_floor)#20
Closed
ChrisRackauckas-Claude wants to merge 1 commit into
Closed
Conversation
The Downgrade Sublibraries caller relied on the centralized sublibrary-downgrade.yml default julia-version "lts". That alias is forwarded verbatim to julia-downgrade-compat's resolver as `resolve.jl --julia=lts`, which only accepts a numeric registry-compat spec and fails with `Invalid compat version spec: --julia=lts`. Pinning to the numeric sublibrary floor "1.10" (the same runtime lts already resolved to) fixes resolution. Config-only. 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.
Problem
The
Downgrade Sublibrariesworkflow fails at thejulia-actions/julia-downgrade-compat@v2step (before buildpkg/runtest) for everylib/*sublibrary, e.g.:Root cause: the caller did not set
julia-version, so it inherited the centralizedsublibrary-downgrade.yml@v1default of"lts". That value is forwarded verbatim intojulia-downgrade-compat's sublibrary resolver asresolve.jl --julia=lts. The resolver only accepts a numeric registry-compat version spec (e.g.1.10), not theltschannel alias, so resolution aborts.This is config-only. The Julia runtime is unaffected:
ltsalready resolved to1.10.11at the setup step, and the sublibrary[compat] juliafloor is"1.10", so pinningjulia-version: "1.10"produces the identical runtime while giving the resolver a value it accepts.Pre-existing vs introduced
Downgrade Sublibrariesonmainwas green on 2026-06-07 and flipped to failure on 2026-06-08, coinciding with the move to the centralized sublibrary downgrade workflow. The main (non-sublibrary)Downgradeworkflow is unaffected (it routesltsthroughdowngrade.yml@v1, which converts it to a numeric spec) and stays green.Change
Set
julia-version: "1.10"(the numeric sublibrary floor) in.github/workflows/DowngradeSublibraries.yml. NoProject.toml, source, or test changes.actionlintpasses.Ignore until reviewed by @ChrisRackauckas.
🤖 Generated with Claude Code