Fix downgrade CI config (julia_floor)#1224
Closed
ChrisRackauckas-Claude wants to merge 1 commit into
Closed
Conversation
The Downgrade Sublibraries caller passed julia-version "lts", which is forwarded verbatim to julia-downgrade-compat's resolver as `resolve.jl --julia=lts`. That resolver 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 atjulia-actions/julia-downgrade-compat@v2(before buildpkg/runtest) for thelib/*sublibraries, e.g. forlib/OptimizationLBFGSB:Root cause: the caller passed
julia-version: "lts", which the centralizedsublibrary-downgrade.yml@v1forwards 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. (The fast-cancelled sibling matrix jobs are fail-fast cancellations of the same error.)This is config-only.
ltsalready resolved to1.10.11at setup, and the sublibrary[compat] juliafloor is"1.10", so pinningjulia-version: "1.10"keeps the identical runtime while giving the resolver a value it accepts.Pre-existing vs introduced
Downgrade Sublibrariesonmasterhas been failing on thisltsresolver error since the sublibrary downgrade workflow was centralized. The main (non-sublibrary)Downgradeworkflow is green (it routesltsthroughdowngrade.yml@v1, which converts it to a numeric spec).Change
Set
julia-version: "1.10"(numeric sublibrary floor) in.github/workflows/DowngradeSublibraries.yml; the existingskip: "SymbolicAnalysis"and group env inputs are unchanged. NoProject.toml, source, or test changes.actionlintpasses.Ignore until reviewed by @ChrisRackauckas.
🤖 Generated with Claude Code