revert(protocol): withdraw invalid publisher domain patch#5887
Conversation
8f525e6 to
ae59b2d
Compare
There was a problem hiding this comment.
Argus is not auto-reviewing this PR because it modifies protected paths that require human review (.changeset/training-agent-publisher-domain-filter.md, .changeset/withdraw-publisher-domain-filter.md, static/schemas/source/core/product-filters.json). A human reviewer should review and merge this PR; Argus will resume on subsequent PRs once these changes land on main.
There was a problem hiding this comment.
Argus is not auto-reviewing this PR because it modifies protected paths that require human review (.changeset/training-agent-publisher-domain-filter.md, .changeset/withdraw-publisher-domain-filter.md, static/schemas/source/core/product-filters.json). A human reviewer should review and merge this PR; Argus will resume on subsequent PRs once these changes land on main.
What changed
publisher_domainfilter from theget_productsschemaWhy
The feature was incorrectly backported and published as 3.1.3. Adding an optional field is a minor protocol change, not a patch-eligible change under the stable 3.1.x release contract. The implementation also accepted
publisher_domains[]on products even though the product schema explicitly permits only singularpublisher_domainselectors.This PR restores the schema, implementation, and tests to their state before #5867. It retains minor release classification so the existing
mainVersion Packages PR remains on the 3.2.0 line rather than attempting another 3.1.x patch. Published 3.1.3 artifacts remain immutable and are handled separately as a withdrawn release.Validation
git diff --checkpassedDeployment note
After merge, deploy the cutover Worker with
npm run deploy:cdn-artifacts-cutoverusing Cloudflare credentials for the account that owns theadcontextprotocol.orgzone. Exact 3.1.3 artifact URLs remain available; the deploy only removes 3.1.3 from movable aliases and discovery defaults.