v0.6.2

v0.6.2

v0.6.1

v0.6.1

v0.6.0

v0.6.0

v0.5.2

chore: sync package-lock.json to v0.5.2

v0.5.1

feat(extension): add remote/workspace session location support

Detect whether the extension runs on the UI or workspace side and tag
sessions with their location. Show a remote indicator in the tree view
and use a separate remoteSocketDir setting for workspace-side instances.

v0.5.0

fix: upgrade Go from 1.22 to 1.23 to fix runtime scheduler crash

Go 1.22.12 has a known runtime bug in pidleget/findRunnable that causes
a segfault on index out of range inside the scheduler. Upgrade to 1.23
which does not have this issue.

v0.4.4

style: fix gofmt alignment in frame_test.go

v0.4.2

ci: inject version into binary via ldflags

v0.4.1

fix: kill code-server process group when codetap exits

When codetap run --stdio exits (relay pipe breaks, SSH drops), the
spawned code-server processes (sh wrapper + node) were orphaned and
reparented to init, leaking memory indefinitely.

- Change ServerRunner.Start to return wait/stop functions instead of blocking
- Use Setpgid to put sh+node in their own process group
- Set Pdeathsig as kernel safety net for unexpected codetap death
- Signal the process group (-pgid) instead of just the direct child
- RunStdio now calls stop() when the relay ends, then drains wait()

v0.4.0

relay: client-driven init phase for automatic commit negotiation

The VS Code extension now writes the client's commit hash to a .commit
sidecar file when connecting. The host relay waits for this file (with
the socket listener already up so the session is discoverable), then
sends a FrameInit (0x04) frame to the remote side. The remote provisions
the exact matching VS Code Server version and acknowledges before any
connections are accepted.

This eliminates version mismatch errors in stdio relay mode without
requiring any flags — the commit is negotiated automatically.

Also adds darwin-arm64 (Apple Silicon) to the CI build matrix.