Skip to content

Coven v0.5.0

Latest

Choose a tag to compare

@github-actions github-actions released this 10 Nov 22:53
· 64 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.5.0
d9b9d6a

Coven v0.5.0

This release advances Coven's supported release family to 0.5.x, fixes mobile signed-request replay retention, and pins Coven Code 0.9.0. Source manifests continue to use release-time version stamping.

Changes since v0.4.10:

  • Retains mobile signed-request nonces through their complete accepted signature-validity window, including clock skew and the inclusive expiry boundary, and keeps retired requests expired after an in-process clock rollback.
  • Accepts valid leading-hyphen installation fingerprints in the documented mobile restore command while retaining strict fingerprint and signed-authority validation.
  • Pins Coven Code 0.9.0 using verified release archives for all five engine platforms.
  • Updates rusqlite to 0.41.1 and bundled SQLite to 3.54.1 to address RUSTSEC-2026-0459.
  • Supports maintainer signing-key rotation with exact-key verification against both the tagged source and current main.
  • Adds fresh exact-source publication authorization, pinned release signers and toolchains, and draft-first immutable GitHub releases with receipts and dependency evidence.
  • Repairs optimized Intel macOS commit identity and checks the installed native package against its source identity before release.
  • Tightens scoped Claude launches, including OS sandbox enforcement for scoped writes, and improves setup and PTY lifecycle handling.
  • Recognizes npm-installed provider launchers during setup certification and validates required version metadata before verification can incur provider charges.
  • Adds durable invocation admission and strengthens Ward audit and acknowledgment barriers already delivered on main.
  • Adds opt-in mobile routing v2 foundations, with counter-based rendezvous and authenticated control/recovery handover.

Known limitations:

  • Mobile replay protection remains process-local; it does not provide durable exactly-once execution or automatic application retry.
  • Mobile transport does not guarantee erasure of every secret copy: the locked Snow dependency retains copied keys, and provisioning uses ordinary JSON/HTTP buffers. Closing a channel invalidates it but does not prove memory erasure (#1611).
  • Coven remains pre-1.0 software. Automations Runtime Authority, Psyche conformance, and ordinary-chat memory admission retain their qualification gates. Full seamless mobile reconnection is not claimed.
  • Mobile routing v2 has owner review, not independent third-party review. Physical-device, real-power-loss, Windows-specific and integrated-journey acceptance retain their separate gates. The separate direct WSS application ingress and automatic migration-controller work are outside this release.
  • Routing guarantees are crash-consistency only. Exhausting the four-attempt remote window requires authenticated direct resynchronization; restoring snapshots requires the documented operator restore ceremony and fresh handover.
  • Unix Ward artifact disposal retains the documented same-privilege final verify-to-unlink race (#924). This release does not claim ownership-bound final deletion on Unix. #924 remains open by the maintainer's v0.5.0 disposition.
  • The additional direct-apply atomic evidence and stronger daemon power-loss acceptance in #1640 are deferred from v0.5.0 by the maintainer. Existing delivered Ward guarantees remain the release claim; #1640 stays open.

Migration and recovery:

  • Security fixes target 0.5.x; upgrade the wrapper and selected native package together through the ordinary installer.
  • After upgrading the CLI, run coven engine install, then coven engine status and coven code --version. The CLI upgrade alone preserves an existing managed engine selection, and an explicit COVEN_ENGINE_BIN override continues to take precedence. Verify the resolved path and version after installation.
  • Existing v1 pairings continue until an authenticated v2 handover. Once the v2 protocol floor exists, v1 material is refused even if v2 state is missing or corrupt; use the authenticated direct recovery path.
  • v0.4.11 remains an immutable, unpublished refused release attempt. Do not retag or reuse it; recover forward using a new version.

Provider certification (macOS ARM64):

These successful reports were produced by the same built candidate, d9b9d6a8b9f4775ad7fa0a2d95a9a78004c6d92c, using one authenticated terminal verification turn per provider. The reports certify this source and platform.

Provider CLI version Duration (ms) Result Report SHA-256
codex 0.167.0 11233 completed 99626633644a54798791078e9055c07e3a4c2cbb86b2bcfc9d81fee6f3dfc30a
claude 2.1.322 9607 completed b7ee8ca09a8d2c5ceac3eaca94716db388e63d145970ab87199d9142f33ee386
copilot 1.0.107 14989 completed 968915ede50660af831a66fa30f0ab5399542aeb02ffc91e7c44a0d65539f053