v0.7.1 - Hardening
Warp Bridge for VS Code — v0.7.1
Release date: 2026-04-20
Type: Hardening / patch release on top of v0.7.0.
Highlights
- Warp Drive — Oz CLI source wired (RF-5). The Warp Drive sidebar
now consumes aCompositeDriveSourcethat prefers the Oz CLI and
transparently falls back to the filesystem source when the binary
lacks thedrivesubcommand. No user-visible change until the CLI
ships the endpoints; the fallback path is identical to v0.7.0
production behaviour. - MCP HTTP+SSE end-to-end smoke tests. First three integration
tests walking the full client handshake (open/sse→ consume the
endpointframe → POST atools/callJSON-RPC request → assert the
SSEmessageframe carries the response), plus rejection of unknown
sessionIdand malformed JSON body.
Changes
Added
OzCliService.driveList(category)anddriveGet(id)(sanitised id,
JSON parsing, raw markdown body).src/drive/ozCliDriveRunner.ts— thin adapter implementing
CliDriveRunneroverIOzCliService. Errors propagate unchanged so
CliDriveSource.isNotAvailableErrorcan convert "unknown command"
stderr into the graceful filesystem fallback.test/mcp/integration.test.ts— 3 new SSE+POST end-to-end tests.
Changed
IOzCliServiceextended withdriveList/driveGet. All test
helpers (createMockCli()) updated accordingly.
Metrics
- Tests: 58 files, 868 unit tests, all green.
- Bundle:
dist/extension.jsat 86.22 KB (within the 90 KB
budget). - VSIX: 60.67 KB.
Compatibility
- VS Code engine: unchanged from v0.7.0.
- Settings, commands, MCP surface and Warp Drive UX: unchanged.
- No migration required.
Operational notes
- The
publish.ymlGitHub Actions workflow that targets the VS Code
Marketplace and Open VSX requires a validVSCE_PATsecret. Renew
it before relying on the automated marketplace publish triggered by
thev0.7.1tag.
Links
- Changelog:
CHANGELOG.md - Previous release:
v0.7.0
What's Changed
- chore(release): v0.7.1 kickoff (version bump + changelog) by @sena-labs in #10
- docs(v0.7.1): release notes by @sena-labs in #11
Full Changelog: v0.7.0...v0.7.1