Skip to content

chore(deps): upgrade lerobot to 0.6.0, torch to 2.11.0 - #67

Closed
pham-tuan-binh wants to merge 1 commit into
mainfrom
chore/lerobot-0.6
Closed

chore(deps): upgrade lerobot to 0.6.0, torch to 2.11.0#67
pham-tuan-binh wants to merge 1 commit into
mainfrom
chore/lerobot-0.6

Conversation

@pham-tuan-binh

Copy link
Copy Markdown
Collaborator

What

Upgrades both Python lockfiles:

  • python/uv.lock: lerobot 0.5.1 → 0.6.0, torch 2.10.0 → 2.11.0
  • examples/python/so101/uv.lock: same bumps

lerobot 0.6 also drops several transitive deps (wandb, xxhash, zipp), which is why the diff shrinks the lockfiles.

Why

Prompted by Dependabot alerts #91 and #92 (CVE-2025-3000, memory corruption in torch.jit.script, low severity).

Note: this PR does not clear the alerts. The CVE is only patched in torch 2.13.0. lerobot 0.6 caps torch at <2.12, so 2.11.0 is the newest we can lock. The alerts stay open until lerobot lifts its cap. The vulnerable path requires calling torch.jit.script on untrusted model code, which portal never does, so exposure is minimal in the meantime.

Testing

  • All 47 tests in python/ pass
  • Both lerobot plugins import cleanly and subclass the correct lerobot 0.6 base classes
  • so101 example modules import without errors against 0.6

lerobot 0.6 raises its torch cap from <2.11 to <2.12, so torch
moves from 2.10.0 to 2.11.0. This does not clear CVE-2025-3000
(Dependabot alerts #91/#92), which is only patched in torch
2.13.0, above lerobot's cap. The 0.6 upgrade also drops several
transitive deps (wandb, xxhash, zipp).
@pham-tuan-binh
pham-tuan-binh deleted the chore/lerobot-0.6 branch August 14, 2026 22:13
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