Repository navigation
chore: release package (beta) - #3706
Merged
Merged
Conversation
|
Ladon does not review bot-authored PRs. |
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.25
Minor Changes
list_accounts/sync_accountsidentity objects (account,operator_unit,identity_change,identity_change_preview), reporting delivery states andnotification_configsnow drop every member their schema does not declare, at any depth. Credential-shaped keys,ctx_metadata,authInfoand write-only billing members are still refused outright; onnotification_configsthat newly includes a retainedwebhook_secretorauthentication.signing_secret. These schemas declare no extension point, so in 17.0.0-beta.24 extension members passed through and now they are dropped.@adcp/reporting-storage):assertMaterializationOutcomerefuses 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 withDELIVERY_FAILED. Its invalid-evidence message now names the Zod issue code rather than quoting the adapter's value. NewundeclaredReportingMaterializationMemberson@adcp/sdk/reporting/ledgerlists the offending paths.notexclusion at any depth, including conditional ones:access_tokenonreporting.delivery_ready,setup.urlonaccount.status_changed,staged_updateoncreative.status_changed. Other schema errors are not enforced, so partial payloads still emit.proposal.offerednow carries identifier fields only, likeproposal.created.sync_principalrefuses 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 explicitall_authorized_accounts: true.<too-deep>hit instead of overflowing the stack, andscrubExtensionsthen drops the wholeextorcontextit 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
list_accounts/sync_accountsidentity objects (account,operator_unit,identity_change,identity_change_preview), reporting delivery states andnotification_configsnow drop every member their schema does not declare, at any depth. Credential-shaped keys,ctx_metadata,authInfoand write-only billing members are still refused outright; onnotification_configsthat newly includes a retainedwebhook_secretorauthentication.signing_secret. These schemas declare no extension point, so in 17.0.0-beta.24 extension members passed through and now they are dropped.@adcp/reporting-storage):assertMaterializationOutcomerefuses 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 withDELIVERY_FAILED. Its invalid-evidence message now names the Zod issue code rather than quoting the adapter's value. NewundeclaredReportingMaterializationMemberson@adcp/sdk/reporting/ledgerlists the offending paths.notexclusion at any depth, including conditional ones:access_tokenonreporting.delivery_ready,setup.urlonaccount.status_changed,staged_updateoncreative.status_changed. Other schema errors are not enforced, so partial payloads still emit.proposal.offerednow carries identifier fields only, likeproposal.created.sync_principalrefuses 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 explicitall_authorized_accounts: true.<too-deep>hit instead of overflowing the stack, andscrubExtensionsthen drops the wholeextorcontextit 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