Bump julia-actions/julia-downgrade-compat from 2 to 2.6.2

[dependabot]

Bumps julia-actions/julia-downgrade-compat from 2 to 2.6.2.

Release notes

Sourced from julia-actions/julia-downgrade-compat's releases.

v2.6.2

Bug-fix release.

What's changed

• Resolve recursive path-source dependency floors (#56) — fixes minimum-version resolution for dependencies configured via [sources]/path, including ones selected only by [targets].test. The action now follows active path sources recursively so local monorepo dependencies stay local throughout the locked build and test, reconstructs hard/weak dependencies and extension triggers for path entries instead of losing them on re-resolution, and intersects root/local compat constraints (reporting a conflict if they don't overlap) rather than silently picking one. On Julia 1.11+ and 1.10, test-only path packages' hard non-local dependencies are promoted to root [deps] so Pkg.test can't independently upgrade them above the locked minimum even with allow_reresolve=false. Also fixes a compat-serialization bug where an intersected open-upper-bound range (e.g. two >= constraints) produced an invalid version specifier string on Julia 1.11+ due to a rendering difference from 1.10. See the new "Local path sources" section in the README for details.

Full changelog: julia-actions/julia-downgrade-compat@v2.6.1...v2.6.2

v2.6.1

What's Changed

• no_promote: also exclude a named PURE test-extra (not just weakdeps) by @​ChrisRackauckas-Claude in julia-actions/julia-downgrade-compat#53

Full Changelog: julia-actions/julia-downgrade-compat@v2...v2.6.1

v2.6.0

What's Changed

• Add no_promote: exclude a currently-unresolvable backend (Mooncake) from the merged promotion by @​ChrisRackauckas-Claude in julia-actions/julia-downgrade-compat#52

Full Changelog: julia-actions/julia-downgrade-compat@v2...v2.6.0

v2.5.2

Bug-fix release.

What's changed

• Strip [sources] packages from the merged project before resolution (#51) — fixes unknown package UUID: … resolver errors in the [extras]+[targets].test "merged resolution" path. create_merged_project starts from deepcopy(main_project), so a source package listed directly in the main project's [deps] — a monorepo root or sublibrary that depends on its own unregistered in-repo siblings and pins them via [sources] — survived the deepcopy in [deps]/[compat]/[sources]. The resolver then received those siblings as deps and errored before resolving anything (a caller-supplied skip list does not help, since it only governs [compat] rewriting). The fix mirrors remove_source_packages_from_project from the non-merged path: source packages are stripped from the merged project's [deps]/[compat]/[sources] and re-added to the manifest as path deps after resolution, so the resolved environment stays complete. Reproduced on SciML/OptimalUncertaintyQuantification.jl (a lib/ monorepo); both the root and sublibraries now resolve where the released action errored. Adds a regression test (full suite 101/101).

Full changelog: julia-actions/julia-downgrade-compat@v2.5.1...v2.5.2

v2.5.1

Bug-fix release.

What's changed

• Dedupe main package in manifest after merged resolution (#50) — fixes the "Invalid manifest format … is ambiguous" error introduced in v2.5.0 (#49). For projects using old-style test deps ([extras] + [targets].test) where a test extra transitively depends on the main package, the merged resolve emitted a registry stanza for the main package and the action then appended a second, path-based stanza — leaving two stanzas with the same UUID and breaking Pkg.Types.EnvCache re-parsing. The fix removes any resolver-emitted stanza matching the main package's UUID before appending the path stanza (mirroring the existing [sources] dedupe), so exactly one stanza remains. This was breaking SciML downgrade CI (e.g. LinearSolve.jl).

Full changelog: julia-actions/julia-downgrade-compat@v2.5.0...v2.5.1

v2.5.0

No release notes provided.

v2.4.0

What's Changed

• Support setup-julia channel aliases (lts, pre, min, nightly) for julia_version by @​ChrisRackauckas-Claude in julia-actions/julia-downgrade-compat#47
• Replace resolver-emitted registry entries when re-adding source packages by @​ChrisRackauckas-Claude in julia-actions/julia-downgrade-compat#46

... (truncated)

Commits

• 8d1c08e clarify
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.47%. Comparing base (22b142c) to head (ebc46d8).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #519   +/-   ##
=======================================
  Coverage   97.47%   97.47%           
=======================================
  Files         128      128           
  Lines        7811     7811           
=======================================
  Hits         7614     7614           
  Misses        197      197           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.