Contract changelog

Mesh contract changes from baseline to mesh-v1.0.0-m2

Every material proto change should leave a readable migration trail. This page turns version bumps into an engineering narrative: what changed, what broke, and what clients need to do next.

mesh-v1.0.0-m2

Introduced 2026-07-23

Current

Adds typed VaultCore signer authorization for HSM PKCS#11 signing and removes caller-supplied provider routing from the public contract.

Developer impact

Material contract change. HSM callers must provide VaultCore authorization evidence; Mesh resolves provider profile and key selectors from governed bindings.

mesh-v1.0.0-m1

Introduced 2026-07-21

Superseded

Renames keystore capability values to public cryptographic families such as threshold MPC instead of local simulator names.

Developer impact

Compatibility migration from early M0 naming. Public contracts describe capabilities, not test backends.

mesh-v1.0.0-m0

Introduced 2026-07-20

Baseline

Establishes the first Mesh DKG, signing, session-resume, receipt, client identity, and request/correlation supportability contract.

Developer impact

Initial baseline for Buf breaking checks and generated OpenAPI artifacts.

Version bump checklist

  • Update the protobuf contract first.
  • Regenerate and commit OpenAPI/Swagger artifacts.
  • Bump service, SDK, compatibility, and baseline surfaces when the wire contract changes materially.
  • Update this changelog with migration impact and any breaking behavior.
  • Let the docs deploy publish the updated spec files and rendered version matrix after merge.