Skip to content

Resolve sublibrary downgrade failures behind the old #417 disable (now re-enabled) #498

Description

@ChrisRackauckas-Claude

DowngradeSublibraries.yml was previously disabled (if: false, "waiting on upstream compat fixes. See #417"). The CI-centralization conversion to sublibrary-downgrade.yml@v1 re-enabled it (and now tests all lib/* sublibraries with no exclusions).

So the downgrade-compat failures that motivated #417 will now show up red again. Next step: work through them — for each failing sublibrary, bump the offending dependency's [compat] lower bound to a version that resolves/precompiles under downgrade (the real fix), rather than re-disabling.

See #417 for the original context.

Follow-up from the SciML CI-centralization work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions