Repository navigation
Conversation
Langfuse's current docs send prompt-version and monitor-alert payloads with the event in a top-level type field; the action field the old created sample used is no longer the discriminator. The samples themselves arrive through webhook-registry's sync, which leaves index.json alone for existing providers, so this one field is changed here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
This changes one field.
providers/langfuse/index.jsonnow uses"topic_identifier": "type"in place of"action".Langfuse's current docs show two webhook payloads: prompt-version and monitor-alert. Both name the event in a top-level
typefield ("prompt-version", "monitor-alert"). The oldv1/created.jsonsample keyed offaction, but the docs no longer describe that shape.Every other change from the 2026-11-12 webhook hub batch comes through webhook-registry, not this PR. All the files involved are doc-sourced (they carry a
sourcekey), so the Doc samples guard would fail a direct edit, and the next registry sync would overwrite one anyway. Once the batch's registry changes merge, theregistry-syncpull request will:dataByQuestionCode,outcome), omnara (agent_profile_id,parent_agent_id,root_agent_id) and notifusecontact.created(four consent fields).langfuse/v1/created.jsonand addprompt-version.jsonandmonitor-alert.json.For existing providers the sync never touches
index.json, so the Langfuse discriminator has to change here. The change doesn't depend on merge order, because doc samples carry their owntopic.sourced_onstays at 2026-10-26. It is still the oldest retrieval date for this version, so it does not overstate how fresh the samples are.Checks:
yarn testpasses (26 of 26) andyarn compilepasses. The guard script reports no doc-sourced edits. I also ran the registry'ssync_webhook_samples.pyplan against this branch for these 14 providers: 9 adds, 167 updates and 1 removal, with nothing blocked and no captures affected. With that plan applied to a scratch copy,yarn compilestill passes.🤖 Generated with Claude Code