@palash-cClaude finished @palash-c's task in 1m 10s —— View job
Docs review: Triggers V1 → V2 migration guide
- Read review guidelines (docs-reviewer.md)
- Run
git diff origin/next...HEADto see changes - Review changed files against checklist
- Post review feedback
One issue worth fixing before merge, otherwise this reads well.
🔴 Broken changelog link
triggers-v1-to-v2.mdx:132 links to /reference/changelog#2026-04-27, but there is no /reference/changelog route. The changelog collection is served under /docs/changelog/YYYY/MM/DD (see lib/source.ts:391), and the V2 entry (content/changelog/04-27-26-webhook-triggers-v2.mdx, date: "2026-04-27") resolves to /docs/changelog/2026/04/27. As written this card 404s — and the CI link checker will likely fail the build on it.
Fix:
// Before
<Card href="/reference/changelog#2026-04-27" description="The original V2 announcement and full API reference" />
// After
<Card href="/docs/changelog/2026/04/27" description="The original V2 announcement and full API reference" />
✅ Checks that passed
- Index registration — added to both
index.mdx(Accordion) andmeta.json. Good — this is the most commonly missed step. - Other links —
/docs/setting-up-triggers/creating-triggersand the self-link/docs/migration-guide/triggers-v1-to-v2both resolve. - Components —
Callout,Steps/Step/StepTitle,Cards/Cardare all used elsewhere in the docs; no import gaps. - AI-native style — uses cURL examples against
v3.1endpoints rather than "click here" UI steps, per the docs convention. - Migration framing — correctly states connected accounts carry over (slug + endpoint change, not re-auth) and the "already on V2 → nothing to do" early-out is a nice touch.
Note: I couldn't fully verify the slug-mapping table against the live toolkit trigger configs from here — the PR description says it was verified against them, which I'll take at face value.
Fix the changelog link and this is good to merge.
