Skip to main content

​
At a glance

Choosing today: stable production integrations use 3.0 with wire pin "3.0". 3.1 validation uses the current RC, v3.1.0-rc.7, with wire pin "3.1-rc.7". After GA, 3.1 integrations use wire pin "3.1".
StatusVersionsWire pinWhat it means
Active3.0 (current stable: 3.0.15)"3.0"Stable default for production integrations. Receives feature and security patches.
Validation3.1 (current RC: v3.1.0-rc.7)"3.1-rc.7" during validation; "3.1" at GAFeature-complete minor release validating through RC artifacts. See What’s New in AdCP 3.1 for the final feature set.
Security-only2.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 life2.0.0, 2.1.0—No patches. Migrate to 3.0.
Planned3.2, 4.0—Targets in planned releases.
Wire values are release-precision only. Send "3.0" for the stable 3.0 line, exact pre-release pins such as "3.1-rc.7" while validating 3.1, and "3.1" only after GA. Do not send patch components like "3.0.15" or full semver pre-release values like "3.1.0-rc.7". See patches are not negotiated. Status legend: Active = current stable generation. Validation = feature-complete release candidate, not GA. 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

VersionReleasedNotes
3.0.02026-04-22GA — stable baseline for the 3.x cycle.
3.0.1 through 3.0.102026-04-28 to 2026-05-10Patches. Wire-compatible with 3.0.0.
3.0.11 through 3.0.152026-05-11 to 2026-05-31Patches. 3.0.15 is the latest stable patch. Wire-compatible with 3.0.0.
3.1.0-rc.1 through 3.1.0-rc.72026-05-29 to 2026-06-04Feature-complete 3.1 validation train. Current published RC is v3.1.0-rc.7; use wire pin "3.1-rc.7" during validation and "3.1" only after GA. See What’s New in AdCP 3.1 for the final feature list.
Patches don’t change the wire contract. Upgrading within 3.0.x is always safe. 3.1 RC artifacts validate the next minor release; they are pinned exactly during validation and collapse to the "3.1" wire value at GA. For per-version detail, see Release Notes (curated narrative) and the Changelog (full technical history).

​
Prereleases (superseded)

VersionReleasedNotes
3.0.0-beta.1 through rc.22026-01-26 to 2026-03-15Superseded.
3.0.0-rc.32026-04-01Superseded by GA. See prerelease upgrade notes if you adopted rc.3.

​
2.x — sunsetting

VersionReleasedNotes
2.0.02025-10-15End of life. No patches. Migrate to 3.0.
2.1.02025-10-19End of life. No patches. Migrate to 3.0.
2.5.02025-11-22Security-only through Aug 1, 2026 (UTC).
2.5.12025-12-24Security-only through Aug 1, 2026 (UTC).
2.5.3January 2026Security-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”?

For stable production, 3.0.15 is current; pin your integration to "3.0" (not "3.0.15"). For 3.1 validation, the current published RC is v3.1.0-rc.7; pin to "3.1-rc.7" until GA, then use "3.1". 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 production integration today3.0 (latest stable patch). Pin "3.0" on the wire.
Validating the final 3.1 feature set before GA3.1.0-rc.7. Pin "3.1-rc.7" on the wire, read What’s New in AdCP 3.1, and move to "3.1" at GA.
Running a 2.5.x integrationMigrate to 3.0 before Aug 1, 2026 (UTC). Start with the migration guide.
Running a 2.0 or 2.1 integrationUpgrade now — out of support.
Trying a post-3.1 unreleased featureSee Release Notes, Versioning & Governance, and experimental status.