Skip to content

chore(next): release 10.0.0-beta.13 - #1865

Open
aao-ipr-bot[bot] wants to merge 2 commits into
nextfrom
release-please--branches--next--components--adcp
Open

aao-ipr-bot[bot] wants to merge 2 commits into
nextfrom
release-please--branches--next--components--adcp

Conversation

@aao-ipr-bot

@aao-ipr-bot aao-ipr-bot Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

10.0.0-beta.13 (2026-11-08)

⚠ BREAKING CHANGES

  • protocol: the SDK no longer advertises or accepts AdCP 3.3-beta.4. get_supported_adcp_versions is 3.0, 3.1, 3.2, 3.3-beta.5 and 3.2-rc.7; an adcp_version pin of 3.3-beta.4 or 3.3.0-beta.4 raises ConfigurationError, and a peer that advertises only 3.3-beta.4 for the 3.3 line negotiates down to 3.2. Re-pin to 3.3-beta.5 or omit the pin.

Features

  • protocol: adopt the signed AdCP 3.3.0-beta.5 bundle (#1866) (f45385d)
  • reporting-storage: make the contract-2 ledger upgrade rolling-deploy safe with expand and contract (#1868) (32fee89)

Bug Fixes

  • reporting-storage: refuse a ledger upgraded to storage contract 2 with the real remedy (#1857) (5eebb53)

This PR was generated with Release Please. See documentation.

@aao-secretariat

Copy link
Copy Markdown

Ladon does not review bot-authored PRs.

@aao-ipr-bot
aao-ipr-bot Bot force-pushed the release-please--branches--next--components--adcp branch from e6a01a1 to 159c33c Compare November 8, 2026 04:15
@aao-ipr-bot
aao-ipr-bot Bot force-pushed the release-please--branches--next--components--adcp branch from d8b4fed to e4e3cf6 Compare November 8, 2026 04:48

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants