Skip to content

Only force latest compatible versions on the newest Julia in Tests - #4

Merged
lkdvos merged 1 commit into
mainfrom
force-latest-compat-newest-julia
Oct 1, 2026
Merged

lkdvos merged 1 commit into
mainfrom
force-latest-compat-newest-julia

Conversation

@lkdvos

@lkdvos lkdvos commented Oct 1, 2026

Copy link
Copy Markdown
Member

Ports the change from #3 (TestGroups) to the single-job Tests.yml reusable workflow.

julia-actions/julia-runtest resolves force_latest_compatible_version: auto to true on dependabot/julia* and compathelper/* branches, pinning every [compat] entry to its newest range. On an older Julia this is unsatisfiable as soon as a dependency's newest range drops support for it (e.g. JET 0.12 on Julia 1.10, see QuantumKitHub/TensorKitSectors.jl#111), so the job fails to resolve before running any tests.

  • Apply it only when julia-version == '1'; every other version runs with false.
  • Expose a force-latest-compatible-version input (default auto), matching TestGroups.yml.

Affects callers of Tests.yml: SUNRepresentations.jl, TensorKitTensors.jl, MultiTensorKit.jl.

🤖 Generated with Claude Code

Same change as for TestGroups: `julia-actions/julia-runtest` resolves
`force_latest_compatible_version: auto` to `true` on Dependabot and
CompatHelper branches, which is unsatisfiable on an older Julia as soon as a
dependency's newest range drops support for it.

Restrict it to `julia-version == '1'` and expose
`force-latest-compatible-version` so callers can override it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lkdvos
lkdvos merged commit 68d4e38 into main Oct 1, 2026
@lkdvos
lkdvos deleted the force-latest-compat-newest-julia branch October 1, 2026 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant