Skip to content

Traverse v0.4.0

Choose a tag to compare

View all tags
@enricopiovesan enricopiovesan released this 22 Jun 16:02
· 14 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.4.0
dbbadbf
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.4.0

Release date: 2026-06-22

Traverse v0.4.0 is the manifest and governed model-dependency release. It keeps the v0.3.0 source-build app and MCP consumer baseline intact while adding the application bundle, WASM component manifest, model dependency, local inference provider, trace evidence, and downstream conformance work needed for the next app-facing integration step.

Consumers that need only the first youaskm3 v0.3.0 baseline can remain pinned to v0.3.0. Consumers that need application manifests, component manifests, governed model dependency resolution, or downstream app MVP conformance evidence should move to v0.4.0.

Highlights

  • Adds approved Specs 044-application-bundle-manifest and 045-governed-model-dependency-resolution.
  • Adds application and WASM component manifest validation, including real example manifests for the expedition readiness app.
  • Adds atomic application bundle registration so an app manifest and its component manifests register together or fail together.
  • Adds Traverse CLI creation flows for new app and component manifest scaffolding.
  • Adds governed model dependency contracts, schema validation, deterministic model selection, and evidence for selected and rejected model candidates.
  • Adds a real local Ollama inference provider path while keeping local-provider execution opt-in for CI safety.
  • Exposes model selection evidence through runtime traces and MCP-facing execution reports.
  • Adds downstream app MVP conformance scripts covering app bundle registration, WASM workflow execution, model dependency evidence, HTTP/JSON trace paths, and MCP reporting.
  • Adds lean Traverse ops guidance so long-running project work remains bounded and inspectable.

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 additions are backward-compatible in intent: they add manifest, model, trace, CLI, and conformance 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.4.0 manifest/model 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: #470
  • Governing specs: 001-foundation-v0-1, 004-spec-alignment-gate, 031-supply-chain-hardening, 044-application-bundle-manifest, 045-governed-model-dependency-resolution
Assets 7
Loading