Skip to content

spec: announce 2026-11-30 as the v0.1 manifest issuance end date #336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
imran-siddique merged 1 commit into from
Aug 24, 2026
Merged

spec: announce 2026-11-30 as the v0.1 manifest issuance end date #336

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,19 @@

## Unreleased

### Deprecated

- **[SPEC] Issuing v0.1 manifests ends 2026-11-30** (issue #315, phase 5). From that
date the reference implementation produces v0.2 COSE envelopes only. The date follows
phase 4 completing: `cmcp` and `ca2a` both verify a v0.2 envelope through their real
loader paths and both reject a payload declaring v0.1 under a v0.2 envelope
(`AM-VEC-COSE-012`), so a consumer is exercising v0.2 rather than a test harness.

**Verifying v0.1 manifests is not deprecated and has no end date.** These are audit
records with regulated retention well beyond their 90-day validity, and a verifier that
stops reading them destroys evidence rather than tidying a codebase. Same reasoning as
keeping the `-8` Ed25519 code point acceptable indefinitely.

## [0.11.1] — 2026-08-23

### Fixed
Expand Down
5 changes: 5 additions & 0 deletions spec/agent-manifest-spec-v0.2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,6 +168,11 @@ Verifier requirements:
- MUST check `version` before verifying. If the version is unsupported, MUST return `INCOMPATIBLE_VERSION` rather than silently misinterpreting fields.
- SHOULD support at least the current and one prior minor version.

<!-- CHANGED: #315 phase 5 - announce the v0.1 issuance end date -->
**Issuing v0.1 manifests ends 2026-11-30.** From that date the reference implementation produces v0.2 COSE envelopes only, and a producer SHOULD NOT set `version` to `"0.1"`.

**Verifying v0.1 manifests is not deprecated and has no end date.** Manifests are audit records under retention obligations that outlast their validity by years, so a verifier that stopped reading them would destroy evidence rather than remove code. `INCOMPATIBLE_VERSION` stays reserved for versions a verifier genuinely cannot interpret, never for v0.1.

Compatibility matrix:

| Producer version | Verifier supports | Result |
Expand Down