[jlongster]

Issue for this PR

Closes #

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

Releases the PTY daemon as 0.5.1. It ships Windows pipe mode (#63196): the daemon can now run pipe processes on Windows, mirroring the Unix pipe mode. Protocol stays 8, so there is no protocol change and existing clients keep working.

Bumps packages/process-daemon to 0.5.1 in Cargo.toml, Cargo.lock, and npm/package.json (version and every platform entry in optionalDependencies), the same files as the 0.5.0 release (#62007).

After merging, push the tag at the merged commit to publish:

git tag process-daemon-v0.5.1 <merge-commit> && git push origin process-daemon-v0.5.1

How did you verify your code works?

No version string left at 0.5.0 in Cargo.toml, Cargo.lock or npm/package.json; cargo metadata --locked resolves opencode-pty 0.5.1; cargo fmt --check passes; the diff matches the 0.5.0 release PR. The release workflow checks that the versions agree.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[opencodejr]

Looks good. This is a version-only release bump with nothing to run.

• opencode-pty is 0.5.1 in Cargo.toml and Cargo.lock. In npm/package.json, version and every platform entry in optionalDependencies are 0.5.1, so the release workflow's consistency check should pass.
• PROTOCOL_VERSION is still 8. Since 0.5.0, protocol.rs only changed a doc comment, so existing clients keep working.
• It touches the same files as #62007. @opencode/pty consumers (core, server, cli) stay at 0.5.0 until the package is published, which matches the previous release.

Public API: the code and protocol are unchanged. Once tagged, this publishes @opencode/pty 0.5.1 and its platform packages, which is backwards compatible.

[jlongster]

Superseded by merged release PR #63366.