Repository navigation
chore: release package (beta) - #3721
Merged
Merged
Conversation
|
Ladon does not review bot-authored PRs. |
aao-ipr-bot
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
November 16, 2026 20:03
8f3ef61 to
76be0fe
Compare
aao-ipr-bot
Bot
force-pushed
the
changeset-release/main
branch
from
November 17, 2026 04:52
76be0fe to
64ccfad
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@adcp/sdk@17.0.0-beta.29
Minor Changes
4393a0e: Beta-channel break for beta.6 pins: this SDK advertises and negotiates only the AdCP
3.3-rc.0preview, the first 3.3 release candidate, and no longer packages or advertises3.3-beta.6. A buyer or seller still on beta.6 will not select the 3.3 preview with this release; the pair negotiates a shared stable release (3.2.8, 3.1.31 or 3.0.25) instead. Upgrade both sides together to keep exercising 3.3 preview features. An explicitadcpVersion: '3.3.0-beta.6'(or'3.3-beta.6') pin now fails with a configuration error.Adopt the signed AdCP 3.3.0-rc.0 bundle (tag commit b5ac0e1bf733, sha256 bdcacb0bb548..., cosign-verified), replacing 3.3.0-beta.6. Public types, Zod schemas, tool metadata and the packaged compliance corpus are regenerated from the rc.0 release.
input_requiredis nowinput-required, creative change kindclick_throughis nowclickthrough, and delivery projection end stateunderdeliveryis nowunder_delivery. The generated types follow.passedreplacespass(content-standards verdicts,get_media_buy_artifactslocal_verdict, registry feed compliance tracks),allreplacesglobal(RATE_LIMITEDscope), andfull_namereplacesname(signal onboardermatch_keys). The originals stay valid and deprecated through 3.x. Version projection to a pre-3.3 seller or caller now maps a replacement back to the value it supersedes (passedtopass) instead of dropping it.creative.assignment_operations(adcp#8997), which sellers declare through the newcreative.assignmentOperationscapability option and buyers read fromCreativeCapabilities.assignmentOperations(newly exported withCreativeAssignmentOperation; a compact seller with a creative library must listassign); audience targeting without inline member push (adcp#8996);image_carouselcta_values(adcp#9001).by_packageshould carry a row (adcp#8970), inlinesubmittedbranches are aligned (adcp#8934), andsync_plansaccepts an omittedhuman_review_required(adcp#9007).Patch Changes
extvendor extension point onrefine_proposals.validateRefineProposalsRequest, whichcreateAdcpServerruns before every handler, rejectedexton the request and on finalize and revise refinements withVALIDATION_ERROR, though the schemas allow it.extis now accepted there when it is an object, and every other unknown key is still rejected. Response verification also acceptsexton result items. The request, refinement and result types carry an optionalext.verdict_explanationon storyboard results, with the newStoryboardVerdictExplanationandStoryboardVerdictContributorschemas. It explains why a storyboard failed when no counted step did, and is populated only for owners and operators. The field is nullable and the change is additive.