chore(deps): bump @adcp/sdk to ^7.0.0#4412
Open
bokelley wants to merge 2 commits into
Open
Conversation
Ships the SDK-side fixes for adcp-client#1676–#1680: removes the account-fabrication shim on create_media_buy, fails closed on pre-3.0 PackageRequest shape, skips webhook storyboards without a receiver, surfaces structured adcp_error + validation detail in ComplianceResult.failures[], and grades storyboards not_applicable when required_tools are missing instead of cascading partial to the track. Typecheck clean, 873/873 unit tests pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…reative-builder tenant @adcp/sdk 7.0 narrowed the CreativeBuilderPlatform interface to buildCreative + previewCreative? + listCreativeFormats? + refineCreative? + syncCreatives?. listCreatives and getCreativeDelivery moved to CreativeAdServerPlatform, so /creative-builder no longer advertises them in tools/list. Aligns the tool-catalog drift test (training-agent-tool-catalog-drift.test.ts) with what the SDK actually mounts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Author
CI status`Server integration tests` has one remaining failure: `registry-feed.test.ts > combines multiple type filters with OR`. This failure is pre-existing on `main` (see CI run 25687949037 — same test, same expected/received, same call site) and is not caused by this PR. Root cause is the background crawler writing `property.` / `agent.` events into the test DB between `beforeEach` cleanup and the assertion. Tracked separately in #4413 with a one-line fix. What this PR's CI runs now show
The previous version of this PR (commit `080d20956d`) had two failures; the second one (`training-agent-tool-catalog-drift` for `creative-builder`) was a legitimate consequence of the SDK 7.0 interface narrowing and is fixed in commit `71c21d2fd0`. Safe to admin-merge once a reviewer clears. |
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
Bumps `@adcp/sdk` from `^6.19.1` to `^7.0.0`, which ships the SDK-side fixes for the five compliance-harness issues filed against `adcp-client` after the Wonderstruck probe:
What this changes for AAO grading
Wonderstruck before/after
The 52 surfaced failures are real Wonderstruck-side gaps (lowercase error codes, missing RFC 6750 auth metadata, no RFC 9421 signing, etc.) — 6.19.x was hiding them.
Test plan
🤖 Generated with Claude Code