- Status
- archived
- Published
- 2026-07-30
- Modified
- 2026-07-30
- Category
- product
Included changes
- 01Eligible public change events are enqueued once per configured destination using the existing stable public event identity.
- 02Each request uses the documented HMAC-SHA256 v1 signature headers, an exact HTTPS-origin allowlist and an eight-second timeout.
- 03A persistent outbox and per-attempt ledger record bounded pending, processing, retry, delivered and terminal-failure states without storing receiver bodies.
- 04Administrators can run one bounded cycle or reschedule an eligible failed record; auditors receive the same sanitized read-only view.