dep-bump: quax to >=0.4.3 - #807
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #807 +/- ##
=======================================
Coverage 95.73% 95.73%
=======================================
Files 159 159
Lines 6089 6089
=======================================
Hits 5829 5829
Misses 260 260 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Bumps quax's floor from 0.3.2 to 0.4.3. No code changes needed -- quax.quaxify's public signature is unchanged across this range, so this is a pure version-floor bump. unxt>=2.0 and equinox>=0.13.8 were also considered as part of this sweep, but: - unxt 2.0 is not usable yet: coordinax v0.23.3 (latest, and the ceiling we're holding to) was never updated for unxt 2.0's Quantity/BareQuantity rename, so basic vector construction with range-checking crashes (`eqx.error_if` sees a `Quantity` where it expects a raw JAX array) and other codepaths hit `AttributeError: type object 'Quantity' has no attribute 'type_parameter'`. 154 doctests and 115 tests fail with unxt>=2.0 installed against coordinax 0.23.3. The existing `unxt>=1.11.2,<2` cap (#800) stays until coordinax ships unxt-2.0 support. - equinox was already at >=0.13.8 on main; nothing to bump. Verified: full test suite (1080 passed) and doctests (4964 passed) pass with quax 0.4.3 alone. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
nstarman
force-pushed
the
claude/depbump-quax-unxt-equinox
branch
from
August 14, 2026 14:22
419a1bb to
e2cfe11
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
quax's floor from0.3.2to0.4.3. No code changes needed —quax.quaxify's public signature is unchanged across this range, so this is a pure version-floor bump.unxt>=2.0andequinox>=0.13.8were also considered as part of this sweep, but:unxt>=2.0is not usable yet.coordinaxv0.23.3 (latest release, and the ceiling we're holding to for now) was never updated for unxt 2.0'sQuantity/BareQuantityrename. Concretely: basic vector construction with range-checking crashes (eqx.error_ifinsidecoordinax'scheck_polar_rangereceives aQuantitywhere it expects a raw JAX array →TypeError: ... is not a valid JAX type), and other codepaths hitAttributeError: type object 'Quantity' has no attribute 'type_parameter'. Withunxt>=2.0installed againstcoordinax0.23.3: 154 doctests and 115 tests fail. I checkedcoordinax's GitHub — no open PR or unreleased work brings it up to unxt 2.0 yet. The existingunxt>=1.11.2,<2cap (⬆️ dep-bump: cap unxt below 2.0 #800) stays until it does.equinoxwas already at>=0.13.8onmain— nothing to bump.Verification
pre-commit runon the changed files: clean.🤖 Generated with Claude Code