CI: disable Downgrade workflow until ecosystem stabilizes#4516
Merged
ChrisRackauckas merged 1 commit intoMay 10, 2026
Merged
Conversation
Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.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.
Downgrade CI on master is currently red because the lower-bound resolution can't satisfy the constraint set after the SciMLBase v3 / OrdinaryDiffEq v7 / RecursiveArrayTools v4 ecosystem rollout. Mirroring the pattern in
SciML/OrdinaryDiffEq.jl'sDowngrade.yml(if: falseat the job level), disable the workflow until the ecosystem floors are bumped. The workflow is preserved in tree so it can be re-enabled later.Ignore until reviewed by @ChrisRackauckas.