diff --git a/CHANGELOG.md b/CHANGELOG.md index f53bc8bc519..520daa4088a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -16,7 +16,7 @@ - 8644cdf: Update the TypeScript SDK dependency and current 3.2 RC guidance, certification prompts, conformance metadata, and provenance assertions to `@adcp/sdk@14.0.0-rc.35`. - acab756: Harden the experimental Reliable Reporting consumer-status loop. Reserve `authoritative_party` on `reporting-delivery-config.json` (sellers MUST reject `consumer` with `UNSUPPORTED_FEATURE` until a later minor defines the buyer-deposited revision task) and relax the seller-authoritative billing-feed constraint accordingly. Give a `received` status made stale only by a seller restatement a bounded `delayed` grace window before it escalates. Make the buyer's posting deadline `expected_at + automated_recovery_window_seconds` and surface unmet deadlines through `obligation_counts.consumer_status_pending`, a count that never changes seller health. Add issue lifecycle fields (`opened_at`, `issue_state`, `external_ref`) with optional `consumer_mismatch_escalation_seconds` and `operations_contact` capability advertisement. Add the `content_mismatch` consumer status with a closed `mismatch_code` for contract-fact disagreements, which are explicitly not measurement disputes. Extend the `reporting_core_lifecycle_probe` controller with `restate_after_received` so the grace projection is graded live, and make the reference seller reject the reserved `authoritative_party` value so the normative MUST has working code behind it. -- decd95f: Retire superseded 3.x beta prerelease artifacts from `dist/schemas`, `dist/compliance`, and `dist/protocol`, keeping only the `3.2.0-beta.11` schema bundle (frozen `3.2-beta` documentation selector), `3.2.0-beta.6` (the training agent's retained checkpoint), and `3.1.0-beta.7` (the TypeScript SDK side bundle). This removes about 2 GB from the repository and the runtime image, whose size gate the rc.3 release branch had started to exceed. Previously published beta URLs continue to be served from the artifact CDN on a best-effort basis; documentation now links to the `3.2.0-rc.2` bundle. The immutable-release-artifact guard now permits whole-tree deletion of tagged beta checkpoints while still rejecting in-place edits and any deletion of release-candidate or stable artifacts. +- decd95f: Retire superseded 3.x beta prerelease artifacts from `dist/schemas`, `dist/compliance`, and `dist/protocol`, keeping only the `3.2.0-beta.11` schema bundle (frozen `3.2-beta` documentation selector), `3.2.0-beta.6` (the training agent's retained checkpoint), and `3.1.0-beta.7` (the TypeScript SDK side bundle). This removes about 2 GB from the repository and the runtime image, whose size gate the rc.3 release branch had started to exceed. Previously published beta URLs continue to be served from the artifact CDN on a best-effort basis; documentation now links to the `3.2.0-rc.2` bundle. The beta removal was a one-time repository and runtime-image cleanup. Tagged beta, release-candidate, and stable artifacts that remain are immutable release records: later deletion or in-place modification is rejected. - 8d50c0e: `scripts/run-storyboards-matrix.sh` snapshots the freshly built `dist/schemas/latest` into a temporary directory and runs every tenant against that copy, so a concurrent `npm run build:schemas` in the same tree can no longer abort a tenant with the SDK's schema-root version mismatch. The pre-push hook treats the local matrix as advisory: it is skipped when the working tree has uncommitted changes or when `ADCP_SKIP_STORYBOARD_MATRIX=1`, with the `training-agent-storyboards.yml` workflow as the authoritative gate. - 322e39c: Update the pinned Changesets release action to v2.1.2 and refresh its vendored contract fixture and release-workflow verification. diff --git a/docs/reference/versions.mdx b/docs/reference/versions.mdx index f7ab1bbafa1..63fe0297b04 100644 --- a/docs/reference/versions.mdx +++ b/docs/reference/versions.mdx @@ -13,7 +13,7 @@ description: "Every published AdCP version, its status, and its end-of-life date | Status | Versions | Wire pin | What it means | |---|---|---|---| -| **Release candidate** | 3.2 (current prerelease: `rc.1`) | `"3.2-rc.1"` | Development and staging only. RC.1 is the current signed protocol checkpoint. TypeScript SDK RC.32, Python SDK beta.14, and Go SDK 3.2.1 embed it exactly. Follow the [3.2 prerelease program](/docs/reference/3-2-beta). | +| **Release candidate** | 3.2 (externally exposed candidate: `rc.3`; latest tagged release: `rc.2`) | `"3.2-rc.2"` | Development and staging only. RC.3 artifacts are signed and publicly reachable but have no Git tag or GitHub Release; RC.2 remains the latest official release. Use only exact pins advertised by the peer. Follow the [3.2 prerelease program](/docs/reference/3-2-beta). | | **Active** | 3.1 (current stable: 3.1.20) | `"3.1"` | Current production minor release. See [What's New in AdCP 3.1](/docs/reference/whats-new-in-3-1) for the feature set. | | **Maintained** | 3.0 (current stable: 3.0.26) | `"3.0"` | Supported previous minor for existing production integrations. Receives compatibility and security patches. | | **End of life** | 2.0.0, 2.1.0, 2.5.0–2.5.3 | — | No patches. Migrate to 3.0. See [v2 sunset](/docs/reference/v2-sunset). | @@ -21,7 +21,7 @@ description: "Every published AdCP version, its status, and its end-of-life date **Wire values are release-precision only.** Send `"3.1"` for the stable 3.1 line or `"3.0"` for the maintained 3.0 line. Do not send patch components like `"3.0.19"` or full semver pre-release values like `"3.1.0-rc.15"`. Historical prerelease pins such as `"3.1-rc.15"` remain valid only for agents that explicitly advertise those prerelease values. See [patches are not negotiated](/docs/reference/versioning#patches-are-not-negotiated). -*Status legend: Pending beta = announced but not yet published. Release candidate = immutable prerelease checkpoint for development and staging. Beta = superseded checkpoint; beta bundles are retired from the repository and runtime image once a release candidate exists, and previously published beta URLs are served from the artifact CDN on a best-effort basis only. Active = current stable generation. Maintained = supported previous minor. Security-only = patches for security issues only, no features. End of life = no patches. Planned = not yet released.* +*Status legend: Pending beta = announced but not yet published. Beta and release candidate = immutable prerelease checkpoints for development and staging. A one-time cleanup on 2026-09-14 retired some historical 3.x beta bundles from the repository and runtime image; remaining and future published prerelease artifacts stay immutable, and retired beta URLs are served from the artifact CDN on a best-effort basis only. Active = current stable generation. Maintained = supported previous minor. Security-only = patches for security issues only, no features. End of life = no patches. Planned = not yet released.* ## All published versions @@ -45,7 +45,9 @@ Supported patches don't change the wire contract. Upgrading within 3.0.x is alwa | Version | Released | Notes | |---|---|---| -| **3.2.0-rc.1** | 2026-09-05 | Current protocol checkpoint. Completes the experimental Reliable Reporting 1.0 contract and hardens delivery, reach, and vendor-metric semantics. TypeScript SDK RC.32, Python SDK beta.14, and Go SDK 3.2.1 embed it exactly; use `"3.2-rc.1"` only with peers that explicitly advertise it. | +| 3.2.0-rc.3 | 2026-09-14 (artifact exposure) | Signed candidate artifacts were exposed through R2, but the Release workflow was cancelled and no Git tag or GitHub Release exists. Do not treat RC.3 as an official release; use `"3.2-rc.3"` only for explicit incident validation with peers that advertise it. | +| **3.2.0-rc.2** | 2026-09-13 | Latest tagged and GitHub-released signed protocol checkpoint. Adds the opt-in Reliable Reporting `sync_reporting_status` loop and other additive RC hardening. Use `"3.2-rc.2"` only with peers that explicitly advertise it; the current SDK wave still embeds `3.2.0-rc.1`. | +| 3.2.0-rc.1 | 2026-09-05 | Previous SDK-backed protocol checkpoint. Completes the experimental Reliable Reporting 1.0 contract and hardens delivery, reach, and vendor-metric semantics. TypeScript `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1` embed it exactly; use `"3.2-rc.1"` only with peers that explicitly advertise it. | | 3.2.0-rc.0 | 2026-09-03 | First 3.2 release candidate. TypeScript SDK beta.31 and Python SDK beta.13 embed it exactly; Go SDK 3.2.0 remains generated from beta.9. | | 3.2.0-beta.11 | 2026-09-03 | Previous protocol checkpoint. Adds `get_principal` to the MCP media-buy role profile alongside `sync_principal`, and aligns training-agent and compliance guidance with the beta.10 bundle. TypeScript SDK beta.29 and Python SDK beta.12 embed it exactly. | | 3.2.0-beta.10 | 2026-09-01 | Previous protocol checkpoint. Adds managed reporting delivery, authenticated principals, audio VAST and DOOH support, programmed channel collections, and committed collection selection. TypeScript SDK beta.28 and Python SDK beta.11 embed it. | @@ -98,8 +100,8 @@ Targeted for early 2027. 3.x is mid-cycle — see the [planned releases table](/ | If you are… | Use | |---|---| | Building a new production integration today | **3.1**. Pin `"3.1"` on the wire. | -| Implementing or testing 3.2 without an SDK | Use the signed **3.2 RC.1** artifacts with raw-wire or code-generation workflows. Follow the [prerelease program](/docs/reference/3-2-beta). | -| Running an SDK-backed 3.2 integration test | Pair exact RC.1 wire pin `"3.2-rc.1"` with `@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, or Go `adcp/v3@v3.2.1`. | +| Implementing or testing 3.2 without an SDK | Use the official signed **3.2 RC.2** artifacts and wire pin `"3.2-rc.2"` with raw-wire or code-generation workflows. RC.3 artifacts are externally reachable but not tagged or GitHub-released; use `"3.2-rc.3"` only for explicit incident validation with peers that advertise it. Follow the [prerelease program](/docs/reference/3-2-beta). | +| Running an SDK-backed 3.2 integration test | The current SDK wave (`@adcp/sdk@14.0.0-rc.35`, Python `adcp==8.0.0b14`, and Go `adcp/v3@v3.2.1`) still embeds RC.1 and requires `"3.2-rc.1"`; use raw-wire or regenerated clients for exact RC.2 testing. | | Running an existing 3.0 integration | Stay on **3.0** while you migrate, or move to **3.1** when your SDK and validation are ready. | | Running a 2.5.x integration | Upgrade now — out of support. Start with the [migration guide](/docs/reference/migration). | | Running a 2.0 or 2.1 integration | Upgrade now — out of support. |