chore: migrate Tinybird workspace from Classic to Forward - #68
Conversation
… self-hosted version
Enable ENV configuration for Resend from and replyTo dubinc#2906
…op-2026-07-16 # Conflicts: # apps/web/app/(ee)/api/events/export/route.ts # apps/web/app/(ee)/api/events/route.ts # apps/web/next.config.js # packages/email/src/resend/constants.ts # packages/email/src/send-via-resend.ts # pnpm-lock.yaml
Left out of the import when resolving the merge conflict in packages/email/src/send-via-resend.ts; caught by tsc --noEmit.
- Add FORWARD_QUERY directives to datasources with schema changes (dub_click_events, dub_sale_events, dub_lead_events, dub_api_logs, dub_links_metadata) - Add partner_tag_ids to dub_links_metadata_pipe explicit column list - Add dub_regular_links_metadata_latest datasource and materialization - Add v2 endpoint pipes from Classic workspace (endpoints/ directory) - Add tinybird.config.json for Forward workspace configuration - Add backup script for pre-migration data export
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
These folders do not represent a divergence from upstream. Here is the breakdown:
More importantly, the 18 v2 pipes in
The |
Summary
tinybird.config.jsonrequired by Tinybird ForwardTYPE endpointto v4 analytics pipes so Forward exposes them as HTTP endpointsFORWARD_QUERYblocks after migration completed (they were one-time migration artifacts)pipes/to match upstream structureWhy this is separate from the upstream sync
This is a CFA infrastructure change, not an upstream code change. Upstream manages their own Tinybird workspace separately and is unaffected by this.
Test plan