feat(integrations): push Vercel deployment and uninstall events by webhook
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 35/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- nextjs, playwright, typescript
調査の方向性
Start by reading the webhook contract from #28 and the existing adapter in src/lib/adapters/vercel/ to see how polling currently emits deployment events, then read docs/providers/vercel.md for the signature and envelope details. Work through the handler in order: constant-time HMAC SHA-1 verification of x-vercel-signature on the raw body, dedup on envelope id, team-to-connection mapping, then event mapping and integration-configuration.removed. Cover it with unit tests on recorded payloads plus the Playwright spec for the simulated provider; done is all acceptance boxes green under npm run lint, npm run typecheck, npm test.
索引モデルが issue の本文から書いたものです。
説明
Context
The Vercel adapter (#47, closed) polls deployments hourly. Eddie's decision on #28 (2026-11-14): webhooks first, polling as the backfill, and webhooks are in the MVP. Vercel can push without any new scope: the webhook URL lives on the integration, and deliveries are signed with the client secret the adapter already has.
From docs/providers/vercel.md, "Webhooks (Post-MVP)", checked against Vercel's docs on 2026-10-31:
| Item | Value |
|---|---|
| Where the URL lives | One Webhook URL per integration, set in the Integrations Console, with event checkboxes |
| Signature | x-vercel-signature: hex HMAC SHA-1 of the raw body, keyed with the integration's client secret. Rotating the secret changes the key |
| Envelope | { type, id, createdAt, region, payload }. Deployment payloads carry payload.team.id, payload.project.id, payload.deployment.{id,url,name}, payload.target |
| Delivery | 30 second timeout. Non-2xx responses are retried with backoff for up to 24 hours |
| Useful events | deployment.created, deployment.succeeded, deployment.ready, deployment.error, deployment.canceled, project.created, project.removed, integration-configuration.removed |
| Not pushed | Billing charges and usage. Spend stays polled |
Plan
- Implement the Vercel webhook declaration from the contract #28 adds: verify
x-vercel-signatureagainst the raw body in constant time, deduplicate on the envelopeid. - Map
payload.team.id(or the user id for a personal account) to the connection. Unknown teams are acknowledged and dropped. - Deployment events become the event types the adapter already emits, so a deployment seen by webhook and then by polling shows once.
integration-configuration.removedmarks the connection as needing a reconnect at once.project.createdandproject.removedupdate the connection's accounts without a reconnect, if the adapter's accounts are projects; otherwise ignore them.- Docs:
docs/providers/vercel.md(rename the section to "Webhooks", update uninstall detection and self-hosted registration to set the Webhook URL and events),docs/operations/oauth-apps.md.
Acceptance criteria
- A signed deployment delivery reaches the timeline within a minute, without waiting for a sync.
- A deployment seen by webhook and by polling shows once.
- Unsigned, wrongly signed, or repeated deliveries are rejected or ignored, and logged without their body.
-
integration-configuration.removedmarks the connection as needing a reconnect. - Polling still runs and still fills in charges and any missed delivery.
- Unit tests on recorded, sanitized payloads from Vercel's documented samples. No live calls in CI.
- Playwright e2e: a signed delivery for the simulated Vercel provider appears on the timeline.
Files and areas
src/lib/adapters/vercel/(webhook handler, schemas, fixtures, tests), the webhook route from #28,docs/providers/vercel.md,docs/operations/oauth-apps.md.- Non-goals: new scopes, domain events, and pushing spend (no webhook exists for it).
Verification
npm run lint,npm run typecheck,npm test- The Playwright spec for the simulated delivery.
Depends on
- #28 Ingest provider webhooks (contract, route, deduplication)
- #47 Add the Vercel adapter (closed)
Branch: <issue-number>-vercel-webhooks
Closes with a Closes #<issue-number> footer on the commit or pull request.
Model: anthropic/claude-opus-5-5 | Reasoning effort: unknown
- 主要言語
- TypeScript
- スター
- 1
- フォーク
- 1
- 平均マージ
- 6時間 56分
- マージ済み PR（30日）
- 136
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
eddiejaoude/StackDash のほかの issue
-
area: docs documentation priority: P3 size: S
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
eddiejaoude/StackDash#462 ·
メンテナーはふだん 1 日以内に返信
-
area: web bug priority: P3 size: XS
難易度 1/5 1〜3時間 初心者へのやさしさ 85/100
eddiejaoude/StackDash#432 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
area: database bug priority: P3 size: S
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
eddiejaoude/StackDash#419 ·
メンテナーはふだん 1 日以内に返信
-
area: docs bug priority: P2 size: XS
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
eddiejaoude/StackDash#418 ·
メンテナーはふだん 1 日以内に返信
-
accessibility area: timeline bug priority: P3 size: XS
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
eddiejaoude/StackDash#389 ·
メンテナーはふだん 1 日以内に返信
eddiejaoude/StackDash の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
open-webui/tether#52 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
voidzero-dev/void#835 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
AykutSarac/jsoncrack.com#616 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
melgarafael/DeskcommCRM#4679 ·
メンテナーはふだん 1 日以内に返信