Skip to content
Universal Manifest

Migration Guide: v0.1 to v0.2

Universal Manifest is an open specification. This guide is language-neutral and applies whether your implementation is in TypeScript, Python, Go, Rust, Java, or another runtime.

The full maintainer copy lives at:

  • /Users/grig/work/repo/universalmanifest/docs/guides/MIGRATION-V01-V02.md

What changes in v0.2

Section titled “What changes in v0.2”

v0.2 keeps v0.1’s core fields and forward-compatibility model, but standardizes interoperable integrity verification:

  • manifestVersion becomes "0.2".
  • Signature verification requirements become operational for conformance.
  • Baseline profile: Ed25519 + JCS-RFC8785.

Compatibility at a glance

Section titled “Compatibility at a glance”
  • v0.1 consumers can parse v0.2 payload shape due to unknown-field tolerance, but do not provide v0.2 trust guarantees.
  • v0.2-only consumers should reject unsigned/legacy-only inputs unless dual-version support is explicitly enabled.
  • Mixed environments should run dual-version consumer logic during migration windows.
Section titled “Recommended rollout”
  1. Add dual-version consumer path keyed by manifestVersion.
  2. Upgrade issuers to emit signed v0.2 manifests.
  3. Run both v0.1 and v0.2 conformance evidence during overlap.
  4. Publish and enforce a v0.1 sunset date per deprecation policy.
Section titled “Required governance links”

Next

Section titled “Next”
  • Read the full migration runbook in docs/guides/MIGRATION-V01-V02.md.
  • If starting a net-new implementation, use Implementation Guide.