Skip to content

Traverse v0.16.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 03 Nov 23:52
· 47 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.16.1
e2e09ef
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Released 2026-11-03.

Traverse v0.16.1 is a patch lockstep crate and npm release. It is
additive (no breaking host ABI): catalog model.execute@1.0.0 runs on
published Browser and Node hosts via Spec 1719 / Decision 122. Cut with:

bash scripts/ci/bump_version.sh 0.16.1

This cut stays on the 0.16.x line so the workspace traverse-contracts
version still satisfies published traverse-registry 0.29.0
(traverse-contracts >=0.8.1, <0.17.0) and [patch.crates-io] keeps one
type identity. A later minor needs a registry contracts range bump first.

Highlights

  • Catalog model.execute@1.0.0 on Browser and Node (#1719, #1770,
    Decision 122, Spec 1719). A guest suspends at connector_invoke; the host
    answers asynchronously and resumes through the same Spec 104 checks. No
    exported symbol or bridge ABI version changed.
  • Web APIs: BundleEmbedder.activateMediatedConnector and
    exactModelMediatedConnector (first-party traverse.model-runtime). Use
    submitAsync; sync submit fails with async_submit_required.
  • Fix on every host (Spec 104 1.1.0 FR-008). The output filter no longer
    refuses a signed model_evidence for holding public URLs.
  • Shared cross-host vector: fixtures/cross-host/model-execute-v1 (native
    adds placement_evidence because only native meters fuel).
  • Swift, Android, and .NET activation APIs are not shipped yet.

All changes

Catalog model.execute@1.0.0 runs in Browser and Node (#1719, Decision 122, Spec 1719)

  • A guest can now call a connector the host answers asynchronously. It suspends
    at connector_invoke, and the host's answer resumes it through the same
    Spec 104 checks. No exported symbol or bridge ABI version changed.

  • New in traverse-embedder-web: BundleEmbedder.activateMediatedConnector and
    exactModelMediatedConnector, the first-party traverse.model-runtime binding.
    Use submitAsync for these targets. Sync submit fails them with
    async_submit_required.

  • The published model.execute@1.0.0 now runs unchanged over a signed package in
    Node and on native, with one shared vector in
    fixtures/cross-host/model-execute-v1. Native also adds placement_evidence,
    because only native meters fuel.

  • Fix on every host (Spec 104 1.1.0 FR-008). The output filter no longer refuses
    a signed model_evidence for holding public URLs. Before, a real package failed
    with connector_unavailable. The filter still covers everything else.

  • ExactModelExecution gains output_schema_ref.

  • Swift, Android and .NET activation APIs aren't shipped yet.

  • Minimal Browser and Native examples:
    host-connector-command-dispatch.md.

Dependency bumps since v0.16.0

  • wat 1.262.0 (#1759), tonic-prost 0.14.7 (#1762), zip 9.1.2
    (#1763), wasmparser 0.262.0 (#1761), uuid 1.29.0 (#1760).
  • Swift Package binary target pointed at swift-host-v0.16.0 (#1769).

Digests (at cut)

Artifact Value
Workspace / crates / npm 0.16.1
runtime/runtime.wasm sha256 7a322a17e3fd58f8bd26e915dd81bad68732500dc981499bd280a6d2e6507d52
runtime/runtime-release.json runtime_version 0.16.1, bridge_version 1.1.0, bridge_abi_version 10100
npm traverse-embedder-web@0.16.1 integrity (fill after publish)

Release checklist

  • fixtures/cross-host/model-execute-v1 covered by Node + native tests from #1770.
  • crates.io lists 0.16.1 for published Traverse crates.
  • npm view traverse-embedder-web version → 0.16.1.
  • GitHub Release Traverse v0.16.1 on tag v0.16.1 (Latest).
  • Post-publish: comment digests (npm integrity) on #1719 / #1775.

Links

Assets 3
Loading