mirror of https://github.com/vercel/workflow.git synced 2026-09-14 19:59:43 +08:00

Files

T

History

Pranay Prakash 3859d338e3 Propagate trace context to vercel-workflow.com in workbench instrumentation (#2601 )

* 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.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* 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.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-23 16:13:55 -07:00

astro

fix(deps): upgrade astro to 6.4.6 to resolve CVE-2026-54299 (#2457 )

2026-06-16 14:18:36 -07:00

example

Propagate trace context to vercel-workflow.com in workbench instrumentation (#2601 )

2026-06-23 16:13:55 -07:00

express

chore: bump express and fastify in workbenches (#1499 )

2026-03-23 19:57:08 -07:00

fastify

[nitro] Use nitro v3 functionRules for workflow routes (#1575 )