|
| 1 | +# Traverse v0.3.0 |
| 2 | + |
| 3 | +Release date: 2026-06-06 |
| 4 | + |
| 5 | +Traverse v0.3.0 is the first GitHub Release after the historical `v0.2.0` tag. The `v0.2.0` tag remains part of the repository history, but it was not published as a GitHub Release. Consumers should pin `v0.3.0` for the current app-consumable, supply-chain-hardened baseline. |
| 6 | + |
| 7 | +## Highlights |
| 8 | + |
| 9 | +- Adds the HTTP/JSON application API surface for downstream apps, including local serve, discovery, registration, and execution paths. |
| 10 | +- Adds workspace identity, auth, runtime grants, isolation policy, and audit evidence for app-facing execution. |
| 11 | +- Adds OpenTelemetry-compatible runtime trace export so runtime decisions can be inspected outside Traverse-specific tooling. |
| 12 | +- Adds WASI Host ABI v1 insulation so host imports are validated through a governed compatibility boundary. |
| 13 | +- Adds connector plugin registry and resolution primitives for external integration growth. |
| 14 | +- Adds the portable DataStore runtime model for the AP-leaning state path used by browser/offline-first consumers. |
| 15 | +- Adds governed artifact signature verification, including Ed25519 and Sigstore trust paths. |
| 16 | +- Adds supply-chain hardening evidence, including SBOM generation, provenance evidence, reproducibility checks, and artifact verification. |
| 17 | + |
| 18 | +## Compatibility Notes |
| 19 | + |
| 20 | +- Traverse remains a `0.x` project. Public surfaces are governed and validated, but compatibility is still allowed to evolve before a `1.0` stability commitment. |
| 21 | +- The `v0.2.0` tag exists as a historical workspace version bump and should not be treated as the current published release baseline. |
| 22 | +- No cross-platform binary package is attached to this release. The release publishes source, release notes, and supply-chain evidence artifacts. |
| 23 | + |
| 24 | +## Validation |
| 25 | + |
| 26 | +Release preparation must pass these local gates before tagging: |
| 27 | + |
| 28 | +```bash |
| 29 | +bash scripts/ci/repository_checks.sh |
| 30 | +bash scripts/ci/rust_checks.sh |
| 31 | +bash scripts/ci/coverage_gate.sh |
| 32 | +bash scripts/ci/supply_chain_check.sh |
| 33 | +``` |
| 34 | + |
| 35 | +The GitHub Release should attach the generated supply-chain evidence from `target/supply-chain/`: |
| 36 | + |
| 37 | +- `traverse-sbom.cdx.json` |
| 38 | +- `supply-chain-summary.json` |
| 39 | +- `artifact-verify-report.json` |
| 40 | +- `traverse-cli.provenance.json` |
| 41 | + |
| 42 | +## Traceability |
| 43 | + |
| 44 | +- Release issue: https://github.com/enricopiovesan/Traverse/issues/432 |
| 45 | +- Governing specs: `001-foundation-v0-1`, `031-supply-chain-hardening` |
0 commit comments