ci(downgrade): fix empty-mode regression + add project input#67
Merged
ChrisRackauckas merged 1 commit intoJun 6, 2026
Merged
Conversation
…es, lib/X) downgrade.yml forwarded `projects` only to julia-downgrade-compat, then ran build/test at the repo root (@.), so it couldn't target a workspace submodule or sublibrary (e.g. OptimalUncertaintyQuantification's workspace projects, or lib/X). Add a `project` input (default "@.") passed to julia-buildpkg and julia-runtest, mirroring tests.yml, so a caller can matrix over submodules. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ChrisRackauckas-Claude
changed the title
ChrisRackauckas
added a commit
that referenced
this pull request
Jun 6, 2026
PR #64 added a `mode` input defaulting to "" and passed it through verbatim as `mode: "${{ inputs.mode }}"`. julia-downgrade-compat rejects an empty mode (`mode in valid_modes || error()`, downgrade.jl), so every downgrade.yml@v1 caller that does not set `mode` explicitly errors at the downgrade-compat step before tests run — breaking downgrade CI org-wide. PR #67 added the `project` input but did NOT include this fix, so the regression is still live on @v1. Default `mode` to "deps" and map an explicit empty string to "deps" as well. 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.
Two downgrade.yml fixes — the first is urgent (org-wide regression):
Empty-
moderegression (BREAKING downgrade CI org-wide). A recently-addedmodeinput defaulted to""and was passed verbatim asmode: "${{ inputs.mode }}".julia-downgrade-compatrejects an empty mode (mode in valid_modes || error(...)→downgrade.jl:22), so everydowngrade.yml@v1caller that doesn't setmodeerrors at the downgrade-compat step. Confirmed live: DASSL#95, SciMLLogging#77, etc. all fail there. Fix: defaultmodeto"deps"and map empty→"deps"in the expression. Merge +v1retag ASAP to un-break downgrade CI everywhere.projectinput (the original purpose): pass--projectto build/test so the workflow can target a workspace submodule orlib/X(default@.).actionlint clean.
🤖 Generated with Claude Code