Repository navigation
Conversation
…n routes Carve-out 5/6 of the API endpoint review (PR #2697), platform surfaces: - members: /v1/members/invite -> /v1/members/invitations (creation sits beside revocation) - organizations: provider-access -> provider-availability (same term as projects) - private channels: instance-connection family (connect rather than deploy/destroy), verified-wallets distinct from the wallet registry, principal-memberships, eligibility and event-label names - helius rings: register-and-initialize, identity-scoped rekey, provision-identity setup - clerk webhook handler no longer claims to only link orgs; admin allowlist -> onboarding-allowlist everywhere it is mounted or served - regenerate served paths, catalogs and route snapshots
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
React Doctor found no new issues. 🎉 Reviewed by React Doctor for commit |
[Medium impact] The route renames affect several API workflows and their dashboard callers. Update both route snapshots before merging; the added Clerk compatibility route makes their exact comparisons fail. SummaryRenames platform API routes and updates dashboard callers, API descriptions, and setup guides.
Reviews (2) · Last reviewed commit: "fix(api): keep signed /webhooks/clerk/li..." · Reviewed by Greptile |
keeganthomp
left a comment
There was a problem hiding this comment.
The Clerk endpoint switch needs a coordinated rollout.
|
|
||
| webhooks.post( | ||
| "/clerk/link-orgs", | ||
| "/clerk", |
There was a problem hiding this comment.
Any Clerk endpoint still configured for /webhooks/clerk/link-orgs now gets 404, including the self-hosting quickstart's configuration. Keep a signed compatibility route during migration and update that guide and its generated AI docs.
|
|
||
| webhooks.post( | ||
| "/clerk/link-orgs", | ||
| "/clerk", |
There was a problem hiding this comment.
The new path misses sdp-infra's /webhooks/clerk/ WAF exemption. With that policy, signed events whose profile or metadata matches OWASP rules receive 403 before verification. Update the exception alongside this switch.
| heliusRings.get("/operations/:operationId", requireAction("helius_rings.read"), getRingsOperation); | ||
| heliusRings.post( | ||
| "/operations/:operationId/execute", | ||
| "/operations/:operationId/resume-execution", |
There was a problem hiding this comment.
The Rings runbook still names POST /operations/:id/execute, so following that recovery instruction now returns 404. Update it to /resume-execution alongside this rename.
…le route docs Address the PR review: Clerk endpoints registered before the webhook rename keep a signed compatibility route on the legacy path, which also stays under the /webhooks/clerk/ prefix of the platform load balancer's WAF exemption until sdp-infra widens that rule; removing the alias then requires updating the exemption in the same change. Update the setup and operator sources that still named removed routes: dev-webhook.sh, .env.local.example, the self-hosting quickstart (plus its generated llms-full.txt), the API README (clerk webhook and admin/onboarding-allowlist paths) and the Rings runbook (operations execute -> resume-execution). Cover the alias with a webhook test.
Comments Outside DiffThese findings could not be posted inline.
|
…n routes
Carve-out 5/6 of the API endpoint review (PR #2697), platform surfaces: