Repository navigation
chore(next): sync main into the 10.x beta line - #1911
Closed
rachitm022 wants to merge 19 commits into
Closed
rachitm022 wants to merge 19 commits into
rachitm022 wants to merge 19 commits into
Conversation
…is contracted (#1867) #1857 refused any ledger whose reporting_configurations has offering_id. The rolling-safe upgrade on next (#1856) adds that column in an expand step but keeps the four-column generation key that 0.1.x writes, until the operator contracts. So 0.1.0b5 would refuse to restart mid-rollout, though it otherwise runs on the expand state unchanged. Refuse only when the configuration primary key includes offering_id, i.e. once the ledger is contracted. That is the same test the packaged SQL's key check makes. Refs #1856 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore(main): release adcp-reporting-storage 0.1.0-beta.5 * chore: normalize prerelease version to PEP 440 --------- Co-authored-by: aao-ipr-bot[bot] <279263549+aao-ipr-bot[bot]@users.noreply.github.com>
…s resolve on ubuntu-26.04 runners (#1890) GitHub's ubuntu-latest moved to ubuntu-26.04, whose system zone database drops the legacy links (US/Pacific, PST8PDT). zoneinfo then raises for them, so tests/test_reporting_period_date.py::test_legacy_zone_aliases_resolve_to_the_canonical_date fails on every 9.x run. Pin tzdata 2026.6 in the dev extra and the dev group, as next already does, so zoneinfo falls back to the IANA package. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ated invocation that carries both members (#1889) * fix(server): read the A2A profile's input member, and refuse parameters when the profile is activated The default A2A parser read only an invocation's `parameters` member. A client following the AdCP A2A profile (@adcp/sdk 16.7.0 on any A2A 1.0 agent) sends `{skill, input}`, so handlers received `{}`: `context` was not echoed and versioned tools failed with VERSION_UNSUPPORTED. The parser now reads `parameters` when present, otherwise `input`, and never merges them, so a caller that does not activate the profile is dispatched exactly as before. A request that activates the profile (A2A-Extensions, or the Message's extensions, names https://adcontextprotocol.org/extensions/adcp/v3) must carry exactly one DataPart with an `input` object; `parameters`, alone or beside `input`, is refused with INVALID_REQUEST before handler entry, as the profile requires. The raw-body receipt path reads the same member. Backport of 3f97994 from next. Refs #1887 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(server): cover the A2A input member and the profile's parameters refusal over the real app Refs #1887 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(server): treat a hand-built A2A context as not activating the profile ADCPAgentExecutor.execute is public, and a context built by hand (an adopter's executor test) may lack RequestContext.requested_extensions or Message.extensions. The profile check now reads both defensively instead of raising AttributeError. Refs #1887 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(server): keep dispatching an activated parameters-only A2A invocation on 9.x, with a deprecation warning 9.x is the stable line, so a patch must not start refusing requests that work today. An invocation that activates the AdCP A2A profile but carries only `parameters`, a missing or non-object `input`, or a DataPart count other than one is still dispatched as before, and a deprecation warning names the profile rule. Only an activated invocation carrying both `parameters` and `input` is refused, since it is ambiguous and no compliant client sends it. adcp 10 refuses every non-conforming activated shape. Refs #1887 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(server): cover the 9.x warn-and-dispatch shapes for an activated A2A invocation Refs #1887 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: aao-ipr-bot[bot] <279263549+aao-ipr-bot[bot]@users.noreply.github.com>
BREAKING CHANGE: Webhook challenge helpers now require seller_agent_url and event_types, and proof challenges require an RFC 9421 WebhookSender; pass legacy delivery authentication alongside that sender.
…ebhook-payload-fix fix(webhooks)!: comply with AdCP 3.2 challenge schema
…count-readiness-fix fix(reporting): resolve dynamic status account readiness
rachitm022
requested review from
KonstantinMirin and
bokelley
as code owners
November 15, 2026 13:54
|
Ladon cannot review this PR until merge conflicts are resolved. |
Collaborator
Author
|
Superseded by a conflict-resolved synchronization branch based on |
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
maininto the 10.xnextlinenextRelease sequencing
This PR must land before publishing another SDK 10 beta. A push to
nexttriggers the dedicatedRelease Please (next)workflow, which should propose10.0.0-beta.18from.release-please-manifest.next.json.The stable
10.0.0proposal in #1898 must remain blocked until the 10.x line is ready for GA; publishing it frommainnow would omit the 312 commits already present onnext.Consumer follow-up
After the beta is published, Scope3's embedded sales agent should move its exact
adcppin from10.0.0b17to the published beta. Noadcp-reporting-storagebump is required by #1910.Tracks Scope3 AI-21766.