mirror of
https://github.com/vercel/workflow.git
synced 2026-09-14 19:59:43 +08:00
github-actions[bot]
04e78129dc
* Propagate trace context to vercel-workflow.com in workbench instrumentation @vercel/otel only propagates W3C trace context to Vercel deployment URLs by default, so outgoing requests to the workflow-server (vercel-workflow.com) got a client span with no `traceparent` header — breaking the APM trace link to workflow-server's spans. Add `instrumentationConfig.fetch.propagateContextUrls` for the workflow-server domain in every workbench that uses @vercel/otel: example, nextjs-turbopack, nextjs-webpack, and sveltekit. The Next.js and SvelteKit apps already declared @vercel/otel but weren't registering it at all; they now do. * Also propagate trace context to the Vercel Queue Service (vercel-queue.com) The workflow-server queue path (@vercel/queue) sends to regional vercel-queue.com subdomains (e.g. iad1.vercel-queue.com) when not using the queues proxy, which were missing a `traceparent` header for the same reason as vercel-workflow.com. Add `/vercel-queue\.com/` to propagateContextUrls in all four workbench instrumentation configs. --------- Signed-off-by: Pranay Prakash <pranay.gp@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Clone of ../nextjs-turbopack
This directory is mostly a clone of the turbopack workbench with nearly everything symlinked to the directory.
The package.json is notably different - it uses --webpack for dev and build modes.
Symlinks
Most files/directories are symlinked to ../nextjs-turbopack:
app/- All files inside are symlinked (not the directory itself)workflows/- Symlinked directoryutil/- Symlinked directorypublic/- Symlinked directoryinstrumentation.ts- Symlinked filepostcss.config.mjs- Symlinked filetsconfig.json- Symlinked fileturbo.json- Symlinked file
A few specific files are NOT symlinked:
app/favicon.ico- Real file (symlink doesn't work with Next.js)app/.well-known/- Generated directory by workflow.gitignore- Real filenext.config.ts- Different configuration (webpack-specific)package.json- Different configuration (--webpackflag)
CI Symlink Resolution
Next.js dev mode doesn't work well with symlinks. In CI, the resolve-symlinks.sh script automatically runs before starting the dev server to replace all symlinks with actual file copies. The script:
- Only runs when
CIenvironment variable is set - Resolves all symlinks in the directory (excluding gitignored files like
node_modules) - Preserves the directory structure while replacing symlinks with real files