Fix downgrade CI config (julia_floor)#199
Closed
ChrisRackauckas-Claude wants to merge 1 commit into
Closed
Conversation
…ngrade The Downgrade Sublibraries caller relied on the reusable workflow's "lts" default for julia-version. sublibrary-downgrade.yml@v1 forwards that value straight into julia-actions/julia-downgrade-compat@v2 as a registry compat spec (--julia=lts), and the downgrade resolver rejects channel aliases: [ERROR] Invalid compat version spec: --julia=lts Every lib/* sublibrary declares julia = "1.10", so pass the numeric LTS floor explicitly. This is config-only; no Project.toml/test/source change. 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.
What
The Downgrade Sublibraries workflow has been failing on
master(the regular Downgrade workflow is green). Every sublibrary job dies in thejulia-actions/julia-downgrade-compat@v2step with:Why
DowngradeSublibraries.ymlpasses nojulia-version, so the reusableSciML/.github/.github/workflows/sublibrary-downgrade.yml@v1uses its default"lts". That reusable workflow forwards the value straight intojulia-downgrade-compat@v2asjulia_version, which the action passes to itsresolver as a registry compat version spec (
--julia=lts). The resolveronly accepts numeric compat versions (e.g.
1.10), not channel aliases likelts, so it errors out before any package resolution happens.(The non-sublibrary
Downgradeworkflow does not hit this — it does not feedltsinto the compat action'sjulia_version— which is why only thesublibrary variant is red.)
Fix (config-only)
Pin the numeric LTS floor explicitly in the caller. Every
lib/*sublibrarydeclares
julia = "1.10"(as does the root), so1.10is both a validsetup-julia channel and a valid
--julia=compat spec, and it satisfies everysublibrary's floor.
No
Project.toml, test, or source changes.Verification
actionlint .github/workflows/DowngradeSublibraries.yml→ clean (rc=0).julia-versionresolves to1.10, which matches thejulia = "1.10"compatfloor of the root and all seven
lib/*sublibraries.Ignore until reviewed by @ChrisRackauckas.