Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
alexbouchardd
approved these changes
Apr 8, 2026
Cover breaking changes: webhook signing defaults (whsec_ prefix, simplified signature header), event destination_id → matched_destination_ids, and delivery metadata timestamp format (Unix → ISO 8601). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signature content/header template changes were from a prior release. Only the whsec_ secret prefix is new in v0.16. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ALERT_CALLBACK_URL removed in favor of OPERATION_EVENTS_* config. Alert defaults changed (failure count 20→100, auto-disable true→false). Redis key scoping is internal, not user-facing. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
New operation events docs cover configuration (topics, sinks), event envelope, all 4 event payloads, and delivery guarantees. Alerts page updated to point to operation events for receiving alerts. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
alexluong
force-pushed
the
docs/upgrade-v0.16
branch
from
9add8ad to
4d5f6c9
Compare
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
docs/pages/features/alerts.mdx
Outdated
Contributor
There was a problem hiding this comment.
We should really just remove this no?
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Per review feedback — alerts are now fully covered by the operation events page. Update cross-references accordingly. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
alexluong
added a commit
that referenced
this pull request
Apr 10, 2026
Ports the v0.16 upgrade guide from #811 into the new Markdoc-based docs structure. Adapts "operation events" prose to "operator events" to match the naming decision on feat/refactor-docs; env vars remain OPERATION_EVENTS_* as defined in code. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
3 tasks
alexluong
added a commit
that referenced
this pull request
Apr 10, 2026
Ports the v0.16 upgrade guide from #811 into the new Markdoc-based docs structure. Adapts "operation events" prose to "operator events" to match the naming decision on feat/refactor-docs; env vars remain OPERATION_EVENTS_* as defined in code. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Summary
whsec_prefix, simplified signature header)destination_idreplaced withmatched_destination_idsresponse_data.bodyis now always a string (previously parsed JSON objects were stored as nested objects) — see fix: store HTTP response body as raw string #723attempts.response_datacolumn migrated from JSONB to TEXT (migration000009) — serialization now handled in application code, consistent withevents.dataandattempts.event_dataNote
PR #723 adds two additional breaking changes that should be included in the v0.16 upgrade guide:
response_data.bodyis now always a raw string, even when the destination returnsapplication/json. Previously, JSON response bodies were parsed into objects.attempts.response_datacolumn is migrated from JSONB to TEXT (migration000009). Queries that traverse intoresponse_datavia JSON operators (e.g.,response_data->'body'->>'key') will stop working.🤖 Generated with Claude Code