Skip to content

v0.4.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Apr 14:24
· 100 commits to main since this release
v0.4.0
7103a80

Build Artifacts

Binaries

  • jvs-linux-amd64 - Linux x86_64
  • jvs-linux-arm64 - Linux ARM64
  • jvs-darwin-amd64 - macOS x86_64
  • jvs-darwin-arm64 - macOS ARM64 (Apple Silicon)
  • jvs-windows-amd64.exe - Windows x86_64
  • SHA256SUMS - SHA-256 hashes for the published binaries

Verification

All binaries are signed using Sigstore/cosign. Download the binary with its matching .sig and .pem sidecars; see docs/SIGNING.md for the full guide.

cosign verify-blob jvs-linux-amd64 \
  --signature jvs-linux-amd64.sig \
  --certificate jvs-linux-amd64.pem \
  --certificate-identity=https://github.com/agentsmith-project/jvs/.github/workflows/ci.yml@refs/tags/v0.4.0 \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com

Verify the checksum file with SHA256SUMS.sig and SHA256SUMS.pem, then run sha256sum -c --ignore-missing SHA256SUMS.

  • For tag-push releases, the signing certificate identity is the tag ref, for example refs/tags/v0.4.0.
  • For manual workflow_dispatch releases, artifacts are checked out from refs/tags/v0.4.0 and published as v0.4.0, but the signing certificate identity remains the workflow ref (refs/tags/v0.4.0) that launched the run.

Breaking changes

  • None for the stable v0 public CLI contract.

Known limitations

  • v0 does not include remote push/pull, in-JVS signing commands, partial checkpoint contracts, compression contracts, merge/rebase, or complex retention policy flags.
  • Full verification reads checkpoint payloads and can be I/O intensive on large workspaces.
  • Descriptor signing and in-JVS trust policy remain outside the stable v0 repository format.

Risk labels

  • integrity: descriptor checksum and payload hash detect independent corruption; coordinated descriptor-plus-checksum rewrite remains a v0 residual risk.
  • migration: runtime operation state must be rebuilt at the destination with jvs doctor --strict --repair-runtime; exclude active .jvs/locks/, .jvs/intents/, and .jvs/gc/*.json during physical backup or storage sync.

Migration notes

  • Existing repositories do not need an on-disk migration for this release.
  • After upgrading, run jvs doctor --strict and jvs verify --all on a representative repo.
  • After physical backup or storage migration, exclude active .jvs/locks/, .jvs/intents/, and .jvs/gc/*.json, then run jvs doctor --strict --repair-runtime at the destination before verification.
Assets 20
Loading