Skip to content

Traverse v0.5.0

Choose a tag to compare

View all tags
@enricopiovesan enricopiovesan released this 27 Jun 00:21
· 4 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.5.0
decc2d7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Traverse v0.5.0

Release date: 2026-06-26

Traverse v0.5.0 is the public CLI app registration release. It keeps the v0.4.0 manifest and governed model-dependency baseline intact while adding the public downstream app setup commands, durable local workspace registration state, runtime loading from that state, and conformance evidence needed for downstream apps to bootstrap without private Traverse internals.

Consumers that need only application manifests and governed model dependency evidence can remain pinned to v0.4.0. Consumers that need stable traverse-cli app validate and traverse-cli app register setup flows should move to v0.5.0.

Highlights

  • Adds approved Spec 046-public-cli-app-registration.
  • Adds traverse-cli app validate --manifest <path> --json as the public read-only downstream app validation surface.
  • Adds traverse-cli app register --manifest <path> --workspace <workspace-id> --json as the public local workspace registration surface.
  • Persists validated app registration evidence under .traverse/workspaces/<workspace-id>/apps/<app-id>/<version>/registration.json.
  • Adds runtime loading from CLI-produced workspace app state so registered capabilities and workflows can be discovered without private setup code.
  • Adds downstream public app registration smoke coverage and wires it into downstream app MVP conformance.
  • Documents the boundary clearly: CLI app registration is local-dev workspace setup, not an HTTP app registration endpoint, service registry, downstream UI deployment mechanism, or runtime-owned admin API.

Compatibility Notes

  • Traverse remains a 0.x project. Public surfaces are governed and validated, but compatibility can still move before a 1.0 stability commitment.
  • The v0.3.0 public compatibility documents remain the historical first youaskm3 release baseline.
  • The v0.4.0 application manifest and governed model dependency surfaces remain available.
  • The v0.5.0 additions are backward-compatible in intent: they add public CLI setup and workspace-state loading surfaces rather than removing the v0.3.0 HTTP/JSON or MCP paths.
  • No cross-platform binary package is attached to this release. The release publishes source, release notes, and supply-chain evidence artifacts.

Validation

Release preparation must pass these local gates before tagging:

bash scripts/ci/repository_checks.sh
bash scripts/ci/rust_checks.sh
bash scripts/ci/coverage_gate.sh
bash scripts/ci/supply_chain_check.sh

The downstream app MVP conformance path should also pass for the v0.5.0 public CLI registration baseline:

bash scripts/ci/downstream_app_mvp_conformance.sh

The GitHub Release should attach the generated supply-chain evidence from target/supply-chain/:

  • traverse-sbom.cdx.json
  • supply-chain-summary.json
  • artifact-verify-report.json
  • traverse-cli.provenance.json

Traceability

  • Release issue: #488
  • Governing specs: 001-foundation-v0-1, 004-spec-alignment-gate, 031-supply-chain-hardening, 046-public-cli-app-registration
  • Implementation issues: #482, #483, #484, #485, #486, #487
Assets 7
Loading