Versions & Compatibility

Every published AdCP version, its status, and its end-of-life date. Start here if you’re choosing or upgrading a version.

At a glance

Status	Versions	Wire pin	What it means
Active	3.0 (current: 3.0.11)	"3.0"	Default for new integrations. Receives feature and security patches.
Security-only	2.5.0, 2.5.1, 2.5.3	"2.5"	Security patches through August 1, 2026 (UTC). Not safe for AAO-network production — see v2 sunset.
End of life	2.0.0, 2.1.0	—	No patches. Migrate to 3.0.
Planned	3.1, 3.2, 4.0	—	Targets in planned releases.

Wire values are release-precision only. Send "3.0", not "3.0.11" — a patch component on the wire is rejected. See patches are not negotiated.

Status legend: Active = current generation, receiving feature work. Security-only = patches for security issues only, no features. End of life = no patches. Planned = not yet released.

All published versions

3.x — current generation

Version	Released	Notes
3.0.0	2026-04-22	GA — stable baseline for the 3.x cycle.
3.0.1 through 3.0.10	2026-04-28 to 2026-05-10	Patches. Wire-compatible with 3.0.0.
3.0.11	2026-05-11	Latest published patch.

Patches don’t change the wire contract. Upgrading within 3.0.x is always safe. For per-version detail, see Release Notes (curated narrative) and the Changelog (full technical history).

Prereleases (superseded)

Version	Released	Notes
3.0.0-beta.1 through rc.2	2026-01-26 to 2026-03-15	Superseded.
3.0.0-rc.3	2026-04-01	Superseded by GA. See prerelease upgrade notes if you adopted rc.3.

2.x — sunsetting

Version	Released	Notes
2.0.0	2025-10-15	End of life. No patches. Migrate to 3.0.
2.1.0	2025-10-19	End of life. No patches. Migrate to 3.0.
2.5.0	2025-11-22	Security-only through Aug 1, 2026 (UTC).
2.5.1	2025-12-24	Security-only through Aug 1, 2026 (UTC).
2.5.3	January 2026	Security-only through Aug 1, 2026 (UTC). Last 2.x release.

After August 1, 2026 (UTC), the entire 2.x line is fully deprecated. The 2.x schema URLs continue to resolve so existing integrations don’t break silently, but those schemas receive no further updates. See v2 Sunset for migration paths.

FAQ

What’s “current”?

3.0.11. Pin your integration to "3.0" (not "3.0.11") — wire values use release precision. See Version negotiation.

What happened to 2.2, 2.3, 2.4, 2.6?

The 2.x line skipped version numbers during its working-group cycle. Some appear as in-flight changelog entries but were never released — the changes were rolled forward into the next published version or deferred to 3.0. The five published 2.x releases are 2.0.0, 2.1.0, 2.5.0, 2.5.1, and 2.5.3.

Can I still register a v2 agent?

Yes — v2 agents can be registered in the AAO registry but cannot be AAO Verified. Certification and verified-default discovery require v3.x. See v2 Sunset → If you use the AAO registry.

How long will 3.0 be supported?

At least 12 months after 4.0 GA. See Versioning → Support window for previous major.

Where is 4.0?

Targeted for early 2027. 3.x is mid-cycle — see the planned releases table.

Choosing a version

If you are…	Use
Building a new integration today	3.0 (latest patch). Pin "3.0" on the wire.
Running a 2.5.x integration	Migrate to 3.0 before Aug 1, 2026 (UTC). Start with the migration guide.
Running a 2.0 or 2.1 integration	Upgrade now — out of support.
Trying an unreleased feature	See prerelease upgrade notes and experimental status.

Related

• Versioning & Governance — release tiers, schema-change scope, cadence policy
• v2 Sunset — full v2 end-of-life timeline and migration paths
• What’s new in v3 — feature-by-feature summary of what 3.0 adds
• Release Notes — curated narrative for each version
• Changelog — full technical change history