What changed in v0.5.0

Universal Manifest v0.5.0, published 2026-11-08 as tag v0.5.0 of UniversalManifest/universal-manifest. Compared with the published v0.4 document set.

In one line. v0.5 tightens what a signature accepts and what it covers, adds a second signature profile, and is released as a mechanism with reference suppliers, at conformance level "none".

Each item links to the specification text that states it. Where this page and the specification differ, the specification governs. The full release notes are on GitHub.

Version and migration

What an implementer must change to produce or accept v0.5 manifests:

Signature rules

Contract clarifications

Conformance suite

What v0.5 does not claim

What moves to v0.6

The protected exchange, with its release obligations, permission outcomes and protected cases, is not part of v0.5. It is planned for v0.6. Overview: Status

Release candidate 1 and the final release

v0.5.0 has the same wire files as release candidate 1 (v0.5.0-rc.1, 2026-11-07): the context, schema.json and the conformance index are byte-identical. A manifest or implementation built against release candidate 1 needs no change. The final release corrects text only. The frozen schema.json description still names release candidate 1, because the file cannot change.

Read the v0.5.0 specification · All versions · How the specification evolved