Uh oh!
There was an error while loading. Please reload this page.
Version Packages (beta) - #1787
Closed
ghost wants to merge 1 commit into
Closed
Conversation
ghost
self-requested a review
as a code ownerApril 16, 2026 22:52
Contributor
Contributor
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests📦 Local Production (2 failed)hono-stable (1 failed):
nextjs-webpack-stable (1 failed):
Details by Category✅ 💻 Local Development
❌ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
❌ Some E2E test jobs failed:
Check the workflow run for details. |
Contributor
📊 Benchmark Results
workflow with no steps💻 Local Development
workflow with 1 step💻 Local Development
workflow with 10 sequential steps💻 Local Development
workflow with 25 sequential steps💻 Local Development
workflow with 50 sequential steps💻 Local Development
Promise.all with 10 concurrent steps💻 Local Development
Promise.all with 25 concurrent steps💻 Local Development
Promise.all with 50 concurrent steps💻 Local Development
Promise.race with 10 concurrent steps💻 Local Development
Promise.race with 25 concurrent steps💻 Local Development
Promise.race with 50 concurrent steps💻 Local Development
workflow with 10 sequential data payload steps (10KB)💻 Local Development
workflow with 25 sequential data payload steps (10KB)💻 Local Development
workflow with 50 sequential data payload steps (10KB)💻 Local Development
workflow with 10 concurrent data payload steps (10KB)💻 Local Development
workflow with 25 concurrent data payload steps (10KB)💻 Local Development
workflow with 50 concurrent data payload steps (10KB)💻 Local Development
Stream Benchmarks(includes TTFB metrics)workflow with stream💻 Local Development
stream pipeline with 5 transform steps (1MB)💻 Local Development
10 parallel streams (1MB each)💻 Local Development
fan-out fan-in 10 streams (1MB each)💻 Local Development
SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
❌ Some benchmark jobs failed:
Check the workflow run for details. |
ghost
force-pushed
the
changeset-release/main
branch
from
April 17, 2026 01:18
aae4c5a to
377ad9eCompare
ghost
force-pushed
the
changeset-release/main
branch
from
April 17, 2026 01:35
db9fc7e to
8cfd0acCompare
ghost
force-pushed
the
changeset-release/main
branch
from
April 17, 2026 14:18
8cfd0ac to
c8807a4Compare![workflow-devkit-release-bot[bot]](https://github.laxmiang.work.gd/r/github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
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/swc-plugin@5.0.0-beta.3
Major Changes
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.@workflow/core@5.0.0-beta.3
Minor Changes
e295baeThanks @pranaygp! - Allowstart()to be called directly inside workflow functionsPatch Changes
354840e]:workflow@5.0.0-beta.3
Minor Changes
e295baeThanks @pranaygp! - Allowstart()to be called directly inside workflow functionsPatch Changes
417c493,e295bae]:@workflow/world-vercel@5.0.0-beta.3
Minor Changes
354840eThanks @TooTallNate! - AddVERCEL_WORKFLOW_SERVER_PROTECTION_BYPASSandVERCEL_WORKFLOW_SERVER_URLenv vars.@workflow/ai@5.0.0-beta.3
Patch Changes
#1544
3f6d98fThanks @iNishant! - Forwardstrict,inputExamples, andproviderOptionstool properties to language model providers, and handletype: 'dynamic'toolsUpdated dependencies [
e295bae]:@workflow/astro@5.0.0-beta.3
Patch Changes
417c493]:@workflow/builders@5.0.0-beta.3
Patch Changes
#1686
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.Updated dependencies [
417c493,e295bae]:@workflow/cli@5.0.0-beta.3
Patch Changes
#1686
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.Updated dependencies [
417c493,e295bae,354840e]:@workflow/nest@5.0.0-beta.3
Patch Changes
#1686
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.Updated dependencies [
417c493]:@workflow/next@5.0.0-beta.3
Patch Changes
#1686
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.Updated dependencies [
417c493,e295bae]:@workflow/nitro@5.0.0-beta.3
Patch Changes
417c493,e295bae]:@workflow/nuxt@5.0.0-beta.3
Patch Changes
@workflow/rollup@5.0.0-beta.3
Patch Changes
#1686
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.Updated dependencies [
417c493]:@workflow/sveltekit@5.0.0-beta.3
Patch Changes
417c493]:@workflow/vite@5.0.0-beta.3
Patch Changes
417c493]:@workflow/vitest@5.0.0-beta.3
Patch Changes
417c493,e295bae]:@workflow/web-shared@5.0.0-beta.3
Patch Changes
e295bae]:@workflow/world-testing@5.0.0-beta.3
Patch Changes
417c493,e295bae]:@workflow/web@5.0.0-beta.3