Release v1.3.0 - #73
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
1 participant
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.
Why
Cut v1.3.0: the SSIK backend (#63) with its four post-merge fixes (#65, #66, #69, #70).
plan(...)and the planner core are unchanged; minor bump for thepycbirrt[ssik]extra, the reducedIKSolverprotocol, and the EAIK deprecation.What
CHANGELOG.md: the Unreleased section becomes 1.3.0 with an intro pointing fallback users at the Fixed section, since the MuJoCo differential fallback was not runnable from the examples in 1.2.0 and its unseeded behavior changed.After merge: tag
v1.3.0and publish the GitHub release with the changelog section as notes.Test plan
uv run pytest tests/: 318 passed, 2 menagerie-gated modules skipped; ruff clean. With the menagerie, the UR5e fallback and SSIK integration tests pass.🤖 Generated with Claude Code