feat(webhooks): add replay-webhook-event tool - #222
Draft
gabrielmfern wants to merge 1 commit into
Draft
Conversation
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.
Adds a tool for the new webhook event replay endpoint.
replay-webhook-eventPOST /webhooks/{webhook_id}/events/{event_id}/replayThe same tool lands in the remote server in the monorepo, with the same name, schema, and output text — another agent is opening that PR in parallel, so both servers stay in sync.
Blocked on the resend-node 6.26.0 npm publish
This bumps
resendto6.26.0forwebhooks.events.replay(), added in resend/resend-node#1087 (merged upstream, not yet published to npm).pnpm install --frozen-lockfilewill fail on this PR as committed until that version reaches the registry: resend/resend-node#1087.Verified locally instead by building against that branch:
pnpm add resend@file:<local resend-node checkout>(dist built there,package.jsonat6.26.0), then ran tests/build/lint against the real package. Before committing,package.jsonandpnpm-lock.yamlwere restored to a plain6.26.0semver pin (nofile:reference) so the diff reads like a normal version bump — itsresend@6.26.0lockfile entry carries the old6.25.0integrity hash as a placeholder and needspnpm installto regenerate it for real once the package is published.Notes
get-webhook-event's shape: same two params (webhookId,eventId), same error format.annotationsobject — same convention ascreate-webhook/update-webhook/remove-webhook.2.19.0, matching how feat(webhooks): add event inspection tools #221 bumped bothresendand the package version in the same PR when it needed a fresh SDK method.Checks
pnpm test: 20 files, 224 passed (run against the local resend-node build described above).pnpm build: clean (run against the local build).pnpm lint: clean — same 3 pre-existing biome warnings incli/resolve.tsandtransports/http.tsas feat(webhooks): add event inspection tools #221, unrelated to this change.node ./scripts/check-dependency-versions.ts: passes against the final committedpackage.json.pnpm install --frozen-lockfileagainst the final committed lockfile: fails with a 404 fetchingresend@6.26.0from the registry, as expected — this is the blocker above, not a lockfile bug.Spec PR: resend/resend-openapi#112
Public API PR: resend/resend-monorepo#9535
SDK method: resend/resend-node#1087
Part of DEV-2005.
Linear: https://linear.app/resend/issue/DEV-2018