Repository navigation
Version Packages (beta) - #8751
aao-release-bot[bot] wants to merge 1 commit into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
2c514b4 to
0297050
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
0297050 to
9d660fd
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
9d660fd to
f920083
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
f920083 to
4c677b7
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
4c677b7 to
6006977
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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
adcontextprotocol@3.3.0-beta.5
Patch Changes
deterministic_testingstoryboard now declares the Acme Outdoor / Pinnacle sandbox account as the owner of its product and pricing-option fixtures, and explicitly scopes media-buy, creative, delivery and budget controller calls to that same consuming account. Its separatetest.exampleaccount-provisioning and account-state checks keep their own identity, with account listing filtered to the effective run account so unrelated visible accounts cannot supply the state-transition account ID. The same filter preserves a caller-selected account ID when the seller does not support buyer account provisioning. This prevents later lifecycle controls from following the account selected bysync_accountsand targeting the wrong sandbox account.security.mdxno longer says two verifiers on different PSL versions are non-conformant against each other, or names PSL libraries. On the trust-record path, a verifier whose list lacks a newly added PRIVATE suffix fails closed. Spec R3a step 1, the threat table, L2 §Grants in trust records, and the trust.jsongranteedescription now say the same.