Promote 6.1.0 beta catalog webhook support to a stable release

[bokelley]

Context

Salesagent PR #561 is now integrated and passing CI against adcp==6.1.0b1.

The implementation depends on the beta for:

• NotificationConfig
• wholesale feed webhook models/events
• webhook destination URL validation policy helpers
• webhook sender/signing helpers used for AdCP 3.1 catalog notifications

Ask

When the team is comfortable with the 6.1.0 beta surface, please cut a stable Python SDK release containing this catalog webhook / signal catalog support.

Why it matters

Downstream sellers can merge against the beta today, but production deployments will be cleaner once the needed AdCP 3.1 webhook/signal catalog models and helpers are available in a non-beta SDK version.

Downstream validation

Prebid Sales Agent PR #561 passes local quality, targeted Docker e2e, pre-push unit/integration, and GitHub CI with adcp==6.1.0b1.

[bokelley]

Triage

Classification: release-tracking
Bucket(s): (no standard bucket — release coordination)
Status: ready-for-human

What the experts said:

• (No expert panel convened — release timing is a human judgment call, not a code change.)

My take: This is a release coordination request, not a code change the triage bot can execute. Four draft PRs are still in flight against the 6.1.0-beta.1 base — #835 (webhook token typed field), #836 (JSON-decode error wrapping), #837 (bot-mitigation error), and #838 (sync_catalogs specialism re-cut) — and merging those first would give the stable release a cleaner surface. To promote to stable: merge pending drafts, update pyproject.toml to version = "6.1.0" + classifier 5 - Production/Stable, and let release-please cut the stable release commit; that's a human go/no-go call.

---

Triaged by Claude Code. Session: https://claude.ai/code/session_015BjZXe6W3WYmpMh2z8xgS5

---

Generated by Claude Code