Skip to content

Narrow compat on Graphs, OMEinsumContractionOrders, DataStructures, OrdinaryDiffEqTsit5 to match resolver#326

Closed
mtfishman wants to merge 1 commit into
mainfrom
mf/narrow-compat-to-match-resolver
Closed

Narrow compat on Graphs, OMEinsumContractionOrders, DataStructures, OrdinaryDiffEqTsit5 to match resolver#326
mtfishman wants to merge 1 commit into
mainfrom
mf/narrow-compat-to-match-resolver

Conversation

@mtfishman
Copy link
Copy Markdown
Member

The Check Compat Bounds check was flagging that several compat entries claim support for versions the workspace resolver can't reach (transitive constraints in external deps keep them pinned lower). Reconcile by narrowing the claims to match reality; widen back when upstream constraints loosen.

Changes

Unified across root + docs + test where the entry appears in multiple subprojects:

  • Graphs: root "1.8", docs "1", test "1.12" → all "1.8 - 1.13" (resolver reaches 1.13.1)
  • OMEinsumContractionOrders: root "0.8.3, 0.9, 1", docs "1.2.2" (caret, allows 1.2.3), test "0.9.5, 1" → all "0.8.3, 0.9, 1 - 1.2.2"

Root-only:

  • DataStructures: "0.18, 0.19""0.18" (resolver reaches 0.18.22; 0.19.x unreachable)

Test-only:

  • OrdinaryDiffEqTsit5: "1.1""1.1 - 1.10" (resolver reaches 1.10.0)

Plus patch version bump.

See ITensorDevelopmentPlans/Projects/Ecosystem/compat_bounds_debt/ for the "test-stricter-than-root" antipattern framing this addresses.

🤖 Generated with Claude Code

…rdinaryDiffEqTsit5 to match resolver

These compat entries claimed support for versions the workspace resolver
can't actually reach (external transitive constraints keep Graphs at
1.13, OMEinsumContractionOrders at 1.2.2, DataStructures at 0.18,
OrdinaryDiffEqTsit5 at 1.10). Tighten to match reality so Check Compat
Bounds passes; widen back whenever upstream constraints loosen.

Root, docs, and test are aligned to the same compat ranges for each
dep that appears in multiple subprojects.
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 23, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.10%. Comparing base (9b9ded5) to head (70d7573).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #326      +/-   ##
==========================================
- Coverage   71.45%   69.10%   -2.35%     
==========================================
  Files          81       81              
  Lines        4029     4027       -2     
==========================================
- Hits         2879     2783      -96     
- Misses       1150     1244      +94     
Flag Coverage Δ
docs ?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 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.

@mtfishman
Copy link
Copy Markdown
Member Author

Superseded by ITensorActions#78, which changed check_compat_bounds.jl to resolve the root package in isolation (ignoring weakdeps and subdir projects). After that change, the compat entries this PR narrows no longer get flagged — EinExprs and the other weakdep/test constraints are out of scope for the check. Closing; we can keep the current permissive specs on main.

@mtfishman mtfishman closed this Apr 23, 2026
@mtfishman mtfishman deleted the mf/narrow-compat-to-match-resolver branch April 23, 2026 16:53
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