Commit 568429d
authored
Tests.yml: disable force_latest_compatible_version on LTS (#75)
## Summary
Skip \`force_latest_compatible_version\` on the LTS leg of the Tests
matrix.
Keep the default (\`auto\`) on current Julia.
## Why
\`julia-actions/julia-runtest\`'s default is
\`force_latest_compatible_version:
auto\`, which pins each dep to the upper end of its declared compat on
bot-
authored PRs — so CompatHelper bumps are actually exercised against the
new
version instead of resolving vacuously.
That's the correct behavior on current Julia. On LTS it produces
spurious
failures whenever a transitive dep hasn't caught up. Concrete example:
[ITensorFormatter.jl#52](ITensor/ITensorFormatter.jl#52)
widens \`JuliaSyntax\` compat to \`\"0.4.10, 1\"\`, but \`JuliaFormatter
2.3\`
(the only version compatible on LTS) pins JuliaSyntax to \`0.4.10\` —
forcing
\`1\` on LTS makes it unsatisfiable. Tests on current Julia pass; tests
on
LTS fail as unresolvable.
In many cases we're fine with a bump being aspirational on LTS while
working on current Julia. Without this change those PRs can never merge
unless the entire upstream LTS chain also catches up — which we can't
always control.
## Result
- **Current Julia**: \`auto\` as before — bump PRs still verified
against the
claimed latest version.
- **LTS**: resolves to whatever's reachable; tests still run, just not
pinned to the upper-end compat.1 parent e179427 commit 568429d
1 file changed
Lines changed: 7 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
153 | 153 | | |
154 | 154 | | |
155 | 155 | | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
156 | 163 | | |
157 | 164 | | |
158 | 165 | | |
| |||
0 commit comments