Skip to content

Set the chopin CLI's version to 0.0.32 - #979

Merged
lavaman131 merged 1 commit into
mainfrom
cli-0.0.32
Nov 21, 2026
Merged

lavaman131 merged 1 commit into
mainfrom
cli-0.0.32

Conversation

@lavaman131

Copy link
Copy Markdown
Collaborator

Bumps apps/connector/package.json (and bun.lock) to 0.0.32 so cli-v0.0.32 can be tagged. This release carries #975 (every agent in an NVX microVM of its own, connector protocol 8), #976 (--install-from), #977 (Atomic 0.10.3 in the Atomic agent's image) and #978 (no nvx run folders left behind, and a retry for OpenVMM's io_uring start failure).

After merging, tagging cli-v0.0.32 runs release-cli, which waits for a person to approve the chopin-cli-release environment before publishing.

Verification: CI.

The release after cli-v0.0.31 runs every agent in an NVX microVM of its own
(connector protocol 8): each coding agent, Planner backend, agent check and image
build, with no process-sandbox fallback, and it refuses a machine that can't run
NVX at pairing and connect. It also builds an agent's image from a host folder
with --install-from, pins Atomic 0.10.3 in the Atomic agent's image, removes the
nvx run folders a forced end left behind, and retries a microVM OpenVMM couldn't
start for want of io_uring. A Chopin that gives work only to protocol 8
connectors tells an older chopin to update.

Co-authored-by: Alex Lavaee <lavaman131@github.com>
@lavaman131
lavaman131 merged commit 79cadd9 into main Nov 21, 2026
26 checks passed
@lavaman131
lavaman131 deleted the cli-0.0.32 branch November 21, 2026 13:44
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