Uh oh!
There was an error while loading. Please reload this page.
Version Packages (beta) - #2428
Merged
Merged
Conversation
Contributor
github-actionsBotforce-pushed
the
changeset-release/main
branch
from
June 15, 2026 16:25
08b1aa3 to
1946718Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
June 15, 2026 19:36
f5539ed to
926a5e7CompareContributorAuthor
📊 Benchmark Results
workflow with no steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 1 step💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 10 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 25 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) workflow with 50 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro Promise.all with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.all with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.all with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro Promise.race with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro workflow with 10 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) workflow with 25 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) workflow with 50 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 10 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 25 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 50 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Stream Benchmarks(includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) stream pipeline with 5 transform steps (1MB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) 10 parallel streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) fan-out fan-in 10 streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
|
ContributorAuthor
🧪 E2E Test Results✅ All tests passed Summary
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
|
karthikscale3
approved these changes
Jun 15, 2026
Uh oh!
There was an error while loading. Please reload this page.
ContributorAuthor
No backport to This is a changesets-generated "Version Packages (beta)" commit consisting solely of release plumbing — version bumps in To override, re-run the Backport to stable workflow manually via |
pranaygp added a commit
that referenced
this pull request
Jun 16, 2026
* origin/main: Small detail panel cleanup (#2459) Fix lazy Next workflow HMR (#2438) Prevent peer dependency-only major bumps (#2437) fix(changesets): only major-bump peer dependents when out of range (#2439) Version Packages (beta) (#2428) otel: explicit traceparent injection + linked-trace mode for bounded per-invocation traces (#2363) [next] Clarify `serverExternalPackages` warning (#2417) Add .swc gitignore handling to builder (#2427) Version Packages (beta) (#2390) [ci] Increase dev.test.ts cleanup hook timeout (#2416) [world-vercel] Switch event endpoints to v4 wire format (#2055) docs: document run idempotency (#2011) Render attr_set events and run attributes in observability UI (#2393) [ci] Fix backport job model slug (#2403) [ci] Comment on PR when backport fails, revert to use opus 4.8 (#2400) Update queue client to 0.3.1 (#2399) fix(deps): upgrade esbuild to 0.28.1 (GHSA-gv7w-rqvm-qjhr) (#2395) test: e2e coverage for run-idempotency conflict-handling strategies (#2387) # Conflicts: # pnpm-lock.yaml
pranaygp added a commit
that referenced
this pull request
Jun 16, 2026
* origin/main: fix(core): make deploymentId 'latest' a no-op in non-Vercel worlds (#2397) fix(deps): upgrade astro to 6.4.6 to resolve CVE-2026-54299 (#2457) Small detail panel cleanup (#2459) Fix lazy Next workflow HMR (#2438) Prevent peer dependency-only major bumps (#2437) fix(changesets): only major-bump peer dependents when out of range (#2439) Version Packages (beta) (#2428) otel: explicit traceparent injection + linked-trace mode for bounded per-invocation traces (#2363) [next] Clarify `serverExternalPackages` warning (#2417) Add .swc gitignore handling to builder (#2427) Version Packages (beta) (#2390) [ci] Increase dev.test.ts cleanup hook timeout (#2416) [world-vercel] Switch event endpoints to v4 wire format (#2055)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@workflow/core@5.0.0-beta.17
Minor Changes
#2363
926a5e7Thanks @karthikscale3! - AddWORKFLOW_TRACE_MODEwith a newlinkeddefault: each workflow/step invocation span is now its own trace root with span links to the delivery and run-origin contexts, instead of one trace spanning the entire run. world-vercel now explicitly injects W3Ctraceparent/tracestate/baggageheaders on outgoing workflow-server requests.Span names are also friendlier: workflow and step spans now use the short function name (e.g.
workflow.execute processOrder,step.execute chargeCard,workflow.start processOrder) instead of the uppercase prefixes and full machine names (WORKFLOW_V2 workflow//./src/jobs/order//processOrder). The full name remains available in theworkflow.name/step.namespan attributes, and newworkflowDisplayName/stepDisplayNamehelpers are exported from@workflow/utils.Behavioral changes to telemetry under the new default (set
WORKFLOW_TRACE_MODE=continuousto restore the previous trace shape exactly; the span-name change applies in both modes):start()no longer contains the workflow's execution spans — navigate via span links or theworkflow.run.idattribute instead.workflow.execute/step.executeinvocation spans (formerlyWORKFLOW_V2/STEP) become parentless roots, which changes parent/child-based queries and service-map edges.WORKFLOW_V2 .../STEP ...span names must switch to the new names.workflow.executespan kind changed frominternaltoconsumer, matching the queue-deliveredstep.executespan (this applies in both modes).Existing attributes and baggage keys are unchanged, and everything remains a no-op when no OpenTelemetry SDK is registered.
Patch Changes
926a5e7]:@workflow/utils@5.0.0-beta.4
Minor Changes
#2363
926a5e7Thanks @karthikscale3! - AddWORKFLOW_TRACE_MODEwith a newlinkeddefault: each workflow/step invocation span is now its own trace root with span links to the delivery and run-origin contexts, instead of one trace spanning the entire run. world-vercel now explicitly injects W3Ctraceparent/tracestate/baggageheaders on outgoing workflow-server requests.Span names are also friendlier: workflow and step spans now use the short function name (e.g.
workflow.execute processOrder,step.execute chargeCard,workflow.start processOrder) instead of the uppercase prefixes and full machine names (WORKFLOW_V2 workflow//./src/jobs/order//processOrder). The full name remains available in theworkflow.name/step.namespan attributes, and newworkflowDisplayName/stepDisplayNamehelpers are exported from@workflow/utils.Behavioral changes to telemetry under the new default (set
WORKFLOW_TRACE_MODE=continuousto restore the previous trace shape exactly; the span-name change applies in both modes):start()no longer contains the workflow's execution spans — navigate via span links or theworkflow.run.idattribute instead.workflow.execute/step.executeinvocation spans (formerlyWORKFLOW_V2/STEP) become parentless roots, which changes parent/child-based queries and service-map edges.WORKFLOW_V2 .../STEP ...span names must switch to the new names.workflow.executespan kind changed frominternaltoconsumer, matching the queue-deliveredstep.executespan (this applies in both modes).Existing attributes and baggage keys are unchanged, and everything remains a no-op when no OpenTelemetry SDK is registered.
workflow@5.0.0-beta.17
Minor Changes
#2363
926a5e7Thanks @karthikscale3! - AddWORKFLOW_TRACE_MODEwith a newlinkeddefault: each workflow/step invocation span is now its own trace root with span links to the delivery and run-origin contexts, instead of one trace spanning the entire run. world-vercel now explicitly injects W3Ctraceparent/tracestate/baggageheaders on outgoing workflow-server requests.Span names are also friendlier: workflow and step spans now use the short function name (e.g.
workflow.execute processOrder,step.execute chargeCard,workflow.start processOrder) instead of the uppercase prefixes and full machine names (WORKFLOW_V2 workflow//./src/jobs/order//processOrder). The full name remains available in theworkflow.name/step.namespan attributes, and newworkflowDisplayName/stepDisplayNamehelpers are exported from@workflow/utils.Behavioral changes to telemetry under the new default (set
WORKFLOW_TRACE_MODE=continuousto restore the previous trace shape exactly; the span-name change applies in both modes):start()no longer contains the workflow's execution spans — navigate via span links or theworkflow.run.idattribute instead.workflow.execute/step.executeinvocation spans (formerlyWORKFLOW_V2/STEP) become parentless roots, which changes parent/child-based queries and service-map edges.WORKFLOW_V2 .../STEP ...span names must switch to the new names.workflow.executespan kind changed frominternaltoconsumer, matching the queue-deliveredstep.executespan (this applies in both modes).Existing attributes and baggage keys are unchanged, and everything remains a no-op when no OpenTelemetry SDK is registered.
Patch Changes
1946718,926a5e7]:@workflow/world-vercel@5.0.0-beta.16
Minor Changes
#2363
926a5e7Thanks @karthikscale3! - AddWORKFLOW_TRACE_MODEwith a newlinkeddefault: each workflow/step invocation span is now its own trace root with span links to the delivery and run-origin contexts, instead of one trace spanning the entire run. world-vercel now explicitly injects W3Ctraceparent/tracestate/baggageheaders on outgoing workflow-server requests.Span names are also friendlier: workflow and step spans now use the short function name (e.g.
workflow.execute processOrder,step.execute chargeCard,workflow.start processOrder) instead of the uppercase prefixes and full machine names (WORKFLOW_V2 workflow//./src/jobs/order//processOrder). The full name remains available in theworkflow.name/step.namespan attributes, and newworkflowDisplayName/stepDisplayNamehelpers are exported from@workflow/utils.Behavioral changes to telemetry under the new default (set
WORKFLOW_TRACE_MODE=continuousto restore the previous trace shape exactly; the span-name change applies in both modes):start()no longer contains the workflow's execution spans — navigate via span links or theworkflow.run.idattribute instead.workflow.execute/step.executeinvocation spans (formerlyWORKFLOW_V2/STEP) become parentless roots, which changes parent/child-based queries and service-map edges.WORKFLOW_V2 .../STEP ...span names must switch to the new names.workflow.executespan kind changed frominternaltoconsumer, matching the queue-deliveredstep.executespan (this applies in both modes).Existing attributes and baggage keys are unchanged, and everything remains a no-op when no OpenTelemetry SDK is registered.
Patch Changes
@workflow/ai@5.0.0-beta.11
Patch Changes
926a5e7]:@workflow/astro@5.0.0-beta.17
Patch Changes
c48d27b]:@workflow/builders@5.0.0-beta.17
Patch Changes
#2427
c48d27bThanks @ijjk! - Add.swcto the builder's default gitignore handling.Updated dependencies [
926a5e7]:@workflow/cli@5.0.0-beta.17
Patch Changes
926a5e7,c48d27b]:@workflow/errors@5.0.0-beta.8
Patch Changes
926a5e7]:@workflow/nest@5.0.0-beta.17
Patch Changes
c48d27b]:@workflow/next@5.0.0-beta.17
Patch Changes
#2417
1946718Thanks @TooTallNate! - Clarify that workflow packages removed fromserverExternalPackagesare still compiled during the build.Updated dependencies [
926a5e7,c48d27b]:@workflow/nitro@5.0.0-beta.17
Patch Changes
926a5e7,c48d27b]:@workflow/nuxt@5.0.0-beta.17
Patch Changes
@workflow/rollup@5.0.0-beta.17
Patch Changes
c48d27b]:@workflow/sveltekit@5.0.0-beta.17
Patch Changes
c48d27b]:@workflow/vite@5.0.0-beta.17
Patch Changes
c48d27b]:@workflow/vitest@5.0.0-beta.17
Patch Changes
926a5e7,c48d27b]:@workflow/web-shared@5.0.0-beta.17
Patch Changes
926a5e7]:@workflow/world-local@5.0.0-beta.18
Patch Changes
926a5e7]:@workflow/world-postgres@5.0.0-beta.16
Patch Changes
926a5e7]:@workflow/world-testing@5.0.0-beta.17
Patch Changes
926a5e7]:@workflow/web@5.0.0-beta.17