Skip to content

docs(release-notes): curated 3.0.1 section#3406

Merged
bokelley merged 1 commit intomainfrom
bokelley/3-0-1-release-notes
Apr 28, 2026
Merged

docs(release-notes): curated 3.0.1 section#3406
bokelley merged 1 commit intomainfrom
bokelley/3-0-1-release-notes

Conversation

@bokelley
Copy link
Copy Markdown
Contributor

Summary

Adds the curated Version 3.0.1 section to `docs/reference/release-notes.mdx` ahead of the cut, plus bumps the FAQ's current-version mention. Lands BEFORE the Version Packages PR (#3042) merges, so the 3.0.1 release ships with the curated narrative already on main.

Frames 3.0.1 as a stable-surface no-op for 3.0-conformant agents with an honest accounting of what did change.

What's in the 3.0.1 narrative

  • Adopter action table — per-audience takeaway: production agent (nothing), SDK consumer (bump `ADCP_VERSION`), governance/TMP implementer (review additive fields), `get_signals` caller using top-level `max_results` (migrate to `pagination.max_results`)
  • Why 3.0.1 exists — skills bundle in `/protocol/3.0.1.tgz`. Re-cutting at 3.0.0 would have invalidated cosign attestations bound to the original 3.0.0 SHA-256.
  • Spec polish — `acquire_rights` validation MUSTs, `get_signals` pagination precedence, URL canonicalization on brand.json agent URLs, v3 envelope integrity schema constraint, format asset codegen titles, inline-enum hoisting
  • Experimental surfaces — governance `mode` field, TMP `seller_agent` field. Cross-links to the experimental-status contract so adopters know why patch-level additions are permitted on those surfaces.
  • Conformance harness — `force_task_completion` and `seed_creative_format` scenarios (sandbox-only)
  • One docs-level deprecation — `get_signals` top-level `max_results` (still works in 3.x; removed in 4.0)

CHANGELOG.md framing (separate concern)

CHANGELOG.md follows the 3.0.0 convention — auto-generated `### Patch Changes` per-PR detail under `## 3.0.1`, with the curated narrative living in release-notes.mdx. The Version Packages PR's CHANGELOG.md content can stay as-is, OR a one-line lead-in can be added before merging:

```

3.0.1

See release notes for the curated narrative.
```

Test plan

  • release-notes.mdx renders in Mintlify (no broken cross-references — all anchors resolve to existing pages: `/docs/reference/experimental-status`, `/docs/reference/url-canonicalization`, `/docs/reference/migration`)
  • Pre-commit hooks pass
  • CI green on PR
  • Land before merging Version Packages PR (Version Packages #3042)

🤖 Generated with Claude Code

Add Version 3.0.1 section to release-notes.mdx ahead of the cut. Frames
3.0.1 as a stable-surface no-op for 3.0-conformant agents and gives an
honest accounting of what did change:

- Skills bundle now ships in /protocol/3.0.1.tgz (the original driver —
  re-cutting at 3.0.0 would have invalidated the cosign attestations
  bound to the original 3.0.0 SHA-256)
- Spec polish: acquire_rights validation MUSTs, get_signals pagination
  precedence, URL canonicalization on brand.json agent URLs, v3
  envelope integrity schema constraint
- Experimental surfaces (governance, TMP) gain small additive fields
  per the experimental-status contract
- Conformance harness gains force_task_completion and seed_creative_format
  scenarios (sandbox-only)
- One docs-level deprecation: get_signals top-level max_results
  (still works in 3.x, removed in 4.0)

Adopter action table makes the per-audience takeaway explicit.

FAQ bumped from 3.0.0 to 3.0.1 as the current GA version.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@bokelley bokelley added this to the 3.0.1 milestone Apr 28, 2026
@bokelley bokelley merged commit fea5f47 into main Apr 28, 2026
17 checks passed
@bokelley bokelley deleted the bokelley/3-0-1-release-notes branch April 28, 2026 12:31
@bokelley bokelley mentioned this pull request Apr 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant