chore: release package (beta)#2246
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
7b361df to
d9eaab2
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@9.0.0-beta.31
Minor Changes
1e57767: feat: strip AdCP 3.1-only request fields when the negotiated target is pre-3.1
BrandReferenceis a closed object (additionalProperties: false) in every AdCP version. The 3.1 inline overridebrand_kit_overridewas added in AdCP 3.1 and does not exist in the 3.0 schema — 3.0 sellers reject requests carrying it.industriesanddata_subject_contestationare declared in AdCP 3.0 GA and are accepted by 3.0 sellers; they are left on the wire. Separately, theget_productsdiscovery webhook (push_notification_config, a 3.1 feature) caused the SDK to throw for pre-3.1 clients.The client now omits 3.1-only fields when the negotiated target is pre-3.1 (the client is pinned below 3.1, or the seller does not advertise 3.1 via
get_adcp_capabilities), degrading gracefully:brand_kit_overrideis stripped from outbound brand references oncreate_media_buy,sync_accounts, andget_products; identity fields (domain,brand_id) and 3.0 fields (industries,data_subject_contestation) are preserved.get_productsdiscovery webhook is skipped (results are polled viatasks/get) instead of throwing. An explicit caller-suppliedpush_notification_configon a pre-3.1 client still throws (unchanged).debug_logsdrift entries (pre31_brand_fields_stripped,pre31_webhook_degraded) so the drops are visible and not silent.The brand strip is keyed on
shouldOmit31Fields(clientVersion, sellerCapabilities)— correct for 3.0-pinned callers today and per-seller when a caller pins to 3.1. The webhook suppression is keyed on the client pin only (isPre31AdcpVersion), since suppression runs beforedetectServerVersionpopulates seller caps.Patch Changes
eeaa641: fix(conformance): skip proposal storyboards when supports_proposals is absent
Treat omitted
media_buy.supports_proposalsas unsupported for proposal lifecyclerequires_capabilitygates, including profiles without raw capabilities.68b8f38: Bump ws to 8.21.0 to resolve high-severity memory exhaustion DoS vulnerability (GHSA-96hv-2xvq-fx4p).