Pin warp-lang below 1.13 - #32
Merged
Merged
Conversation
williamshen-nz
force-pushed
the
warp-lang-pin
branch
from
July 30, 2026 19:50
ab3a34d to
fcb0936
Compare
Both cuRobo and cuTAMP require warp-lang <1.13, so constrain the pypi requirement to keep re-locking off newer, incompatible warp releases. The existing lock (warp 1.12.0) already satisfies this bound, so no lock changes are needed. Split out from #30.
williamshen-nz
force-pushed
the
warp-lang-pin
branch
from
July 30, 2026 19:51
fcb0936 to
2b532ac
Compare
ryanlindeborg
approved these changes
Jul 30, 2026
2 tasks
2 tasks
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
2 participants
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
Splits the
warp-langversion pin out of #30 into its own PR.Both cuRobo and cuTAMP require
warp-lang < 1.13, so this constrains thewarp-langpypi requirement to>=0.9.0,<1.13to keep re-locking off newer, incompatible warp releases.Notes
warp-langto 1.12.0, which satisfies the new<1.13bound, so nopixi.lockchanges are required — this is a one-line manifest change.test-unittask and other pixi changes in Support pick and place next to #30 stay with that PR, as they belong to the config/test work.