Repository navigation
chore(process-daemon): release 0.5.0 - #62007
Conversation
![opencodejr[bot]](https://avatars.githubusercontent.com/in/5497873?s=60&v=4){kind=small}
There was a problem hiding this comment.
The version bump looks complete and consistent. opencode-pty / @opencode/pty and all 8 platform optionalDependencies are at 0.5.0, and nothing in packages/process-daemon is left at 0.4.0. The workflow's npm-side check passes. I couldn't run the Cargo-side check because cargo isn't installed here. Nothing ran beyond that, since the change only bumps versions.
Public API: the published @opencode/pty package goes from 0.4.0 to 0.5.0 and ships protocol 8, which is breaking: a v8 server discards a v7 handoff. OpenCode itself is unaffected until it moves to 0.5.0 in #61876.
The only thing that needs care is merge order. release-process-daemon.yml still hardcodes PROTOCOL_VERSION: 7 while src/protocol.rs is at 8. Pushing process-daemon-v0.5.0 before #62006 lands would fail the --version checks.
09914eb to
2a42156
Compare
There was a problem hiding this comment.
My earlier blocker is addressed. The branch is rebased onto dev, which now includes #62006, so the release workflow reads PROTOCOL_VERSION from src/protocol.rs (8) instead of hardcoding 7. The version bump is unchanged from the commit I reviewed before. Nothing new to raise.
Public API: @opencode/pty goes from 0.4.0 to 0.5.0 with protocol 8, which is breaking: a v8 server discards a v7 handoff. OpenCode stays on 0.4.0 until #61876.
Issue for this PR
Closes #
Type of change
What does this PR do?
Releases the PTY daemon as 0.5.0, with protocol 8 (#61875): pipe processes with an output file,
get/wait/signal/set_metadata,ProcessInfo, splitcreate. Protocol 8 is breaking: a v8 server discards a v7 handoff and starts a fresh daemon.Bumps
packages/process-daemonto0.5.0inCargo.toml,Cargo.lock, andnpm/package.json(versionand every platform entry inoptionalDependencies), the same files as the 0.4.0 release (#60325).Merge #62006 first: the release workflow still hardcodes protocol 7, so its
--versionchecks would fail on this build.After merging, push the tag at the merged commit to publish:
OpenCode keeps using
@opencode/pty0.4.0 until #61876 bumps it.How did you verify your code works?
No version string left at 0.4.0 in
Cargo.tomlornpm/package.json;cargo metadata --lockedresolvesopencode-pty0.5.0; the diff matches the 0.4.0 release PR. The release workflow checks that the versions agree.Checklist
Added by the opencode bot (AI-generated).
Related: #61875, #61876
Public API: publishes @opencode/pty 0.5.0 with breaking protocol 8; OpenCode stays on 0.4.0 until #61876