build(deps): consolidate upgrades and fix compatibility - #397
Merged
Merged
Conversation
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.
Update the dependency pins and uv lockfile together, including the matched MuJoCo/MJX 3.13.0 pair, mypy 2.3.1, Ruff 0.16.8, PyYAML stubs, pytest 9.1.1, tqdm 4.70.1, and kvxopt 1.3.3.2. Upgrade artifact uploads to v7 in both workflows.
The new kvxopt stubs expose incompatible assumptions in the platform-specific solver imports. Resolve that optional backend through a module boundary, preserve the missing-extra error, and cover ARM/x86 package selection when the backend is absent. The wheel smoke test now installs the wheel's declared MuJoCo extra instead of a separate stale 3.11.0 pin.
Supersedes #384, #385, #386, #387, #388, #389, #392, #393, #394, #395, and #396.
Validation: