Skip to content

chore: release package (beta) - #3706

Merged
bokelley merged 1 commit into
mainfrom
changeset-release/main
Nov 14, 2026
Merged

bokelley merged 1 commit into
mainfrom
changeset-release/main

Conversation

@aao-ipr-bot

@aao-ipr-bot aao-ipr-bot Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

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.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@adcp/sdk@17.0.0-beta.25

Minor Changes

  • 3408d45: Restore the closed-schema guarantees that AdCP 3.3.0-beta.6 removed when it opened schemas (fix(schemas): open the 3.3 schemas that were meant to be open adcp#8866). This follows up on the 3.3.0-beta.6 adoption.
    • Account projections keep declared members only. list_accounts/sync_accounts identity objects (account, operator_unit, identity_change, identity_change_preview), reporting delivery states and notification_configs now drop every member their schema does not declare, at any depth. Credential-shaped keys, ctx_metadata, authInfo and write-only billing members are still refused outright; on notification_configs that newly includes a retained webhook_secret or authentication.signing_secret. These schemas declare no extension point, so in 17.0.0-beta.24 extension members passed through and now they are dropped.
    • Managed reporting delivery (@adcp/reporting-storage): assertMaterializationOutcome refuses adapter evidence whose resource, verification or nested evidence carries undeclared members, as it did while the schemas were closed, so an adapter that adds a vendor field fails the delivery with DELIVERY_FAILED. Its invalid-evidence message now names the Zod issue code rather than quoting the adapter's value. New undeclaredReportingMaterializationMembers on @adcp/sdk/reporting/ledger lists the offending paths.
    • Notifications: the runtime validates each payload against its webhook schema and refuses one that violates a not exclusion at any depth, including conditional ones: access_token on reporting.delivery_ready, setup.url on account.status_changed, staged_update on creative.status_changed. Other schema errors are not enforced, so partial payloads still emit. proposal.offered now carries identifier fields only, like proposal.created.
    • Reporting subscriptions: sync_principal refuses a subscription scope whose single member is an unknown selector. Before, such a scope passed validation and the coverage engine treated it as every authorized account. The engine now covers all accounts only for an explicit all_authorized_accounts: true.
    • Bounded walks: credential scanning records a <too-deep> hit instead of overflowing the stack, and scrubExtensions then drops the whole ext or context it could not inspect. The account projections fail with a typed error on values deeper than 256 levels. Reporting-status ingest omits diagnostics whose payload-derived pointer contains a control character (C0 and C1 controls, including CR, LF and ESC, and U+2028/U+2029).

@adcp/reporting-storage@0.3.0-beta.7

Minor Changes

  • 3408d45: Restore the closed-schema guarantees that AdCP 3.3.0-beta.6 removed when it opened schemas (fix(schemas): open the 3.3 schemas that were meant to be open adcp#8866). This follows up on the 3.3.0-beta.6 adoption.
    • Account projections keep declared members only. list_accounts/sync_accounts identity objects (account, operator_unit, identity_change, identity_change_preview), reporting delivery states and notification_configs now drop every member their schema does not declare, at any depth. Credential-shaped keys, ctx_metadata, authInfo and write-only billing members are still refused outright; on notification_configs that newly includes a retained webhook_secret or authentication.signing_secret. These schemas declare no extension point, so in 17.0.0-beta.24 extension members passed through and now they are dropped.
    • Managed reporting delivery (@adcp/reporting-storage): assertMaterializationOutcome refuses adapter evidence whose resource, verification or nested evidence carries undeclared members, as it did while the schemas were closed, so an adapter that adds a vendor field fails the delivery with DELIVERY_FAILED. Its invalid-evidence message now names the Zod issue code rather than quoting the adapter's value. New undeclaredReportingMaterializationMembers on @adcp/sdk/reporting/ledger lists the offending paths.
    • Notifications: the runtime validates each payload against its webhook schema and refuses one that violates a not exclusion at any depth, including conditional ones: access_token on reporting.delivery_ready, setup.url on account.status_changed, staged_update on creative.status_changed. Other schema errors are not enforced, so partial payloads still emit. proposal.offered now carries identifier fields only, like proposal.created.
    • Reporting subscriptions: sync_principal refuses a subscription scope whose single member is an unknown selector. Before, such a scope passed validation and the coverage engine treated it as every authorized account. The engine now covers all accounts only for an explicit all_authorized_accounts: true.
    • Bounded walks: credential scanning records a <too-deep> hit instead of overflowing the stack, and scrubExtensions then drops the whole ext or context it could not inspect. The account projections fail with a typed error on values deeper than 256 levels. Reporting-status ingest omits diagnostics whose payload-derived pointer contains a control character (C0 and C1 controls, including CR, LF and ESC, and U+2028/U+2029).

Patch Changes

  • Updated dependencies [3408d45]
    • @adcp/sdk@17.0.0-beta.25

@aao-secretariat

Copy link
Copy Markdown

Ladon does not review bot-authored PRs.

@bokelley
bokelley merged commit ba35a02 into main Nov 14, 2026
45 checks passed
@bokelley
bokelley deleted the changeset-release/main branch November 14, 2026 01:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant