Uh oh!
There was an error while loading. Please reload this page.
fix(core): bump payload-compression cutoff to 5.0.0-beta.18 - #2470
Merged
Conversation
The gzip/zstd FORMAT_VERSION_TABLE entries were gated on 5.0.0-beta.16, but beta.16 and beta.17 were both published (2026-06-15) before the compression PR (#2394) merged (2026-06-16) — neither contains the compression read path. The next published version is beta.18 (pending Version Packages #2451), which is the first that can decode these payloads. With the cutoff at beta.16, getRunCapabilities() reported beta.16/.17 targets as compression-capable, so a cross-deployment start()/resumeHook() (or a resilient-start probe resolving to such a target) would write zstd/gzip payloads the target cannot decode — silent replay corruption, exactly the TODO(release) hazard noted on those lines. Bump both entries (and the doc comments) to beta.18 and extend the capability test to assert beta.16/beta.17 are treated as incapable.
Contributor
🦋 Changeset detectedLatest commit: 70508f0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
📊 Benchmark Results
workflow with no steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | 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 | Next.js (Turbopack) | Nitro workflow with 25 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro workflow with 50 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Promise.all with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro 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: Next.js (Turbopack) | Nitro | Express Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Nitro | Express Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Promise.race with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) workflow with 10 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro workflow with 25 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Nitro | Express workflow with 50 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | 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: Nitro | Express | Next.js (Turbopack) workflow with 50 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Stream Benchmarks(includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro stream pipeline with 5 transform steps (1MB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro 10 parallel streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) fan-out fan-in 10 streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
|
Contributor
🧪 E2E Test Results✅ All tests passed Summary
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
|
pranaygp
approved these changes
Jun 17, 2026
Uh oh!
There was an error while loading. Please reload this page.
Contributor
No backport to This commit adjusts the version cutoff for the gzip/zstd payload-compression feature introduced by To override, re-run the Backport to stable workflow manually via |
This was referenced Jun 17, 2026
pranaygp added a commit
that referenced
this pull request
Jun 18, 2026
…-hydration * origin/main: perf(core): lazy inline step start (save one world round-trip per step) (#2478) perf(core): skip per-step events.list via inline event-log delta (#2475) Version Packages (beta) (#2491) [world-vercel] Honor hasMore flag from v4 list pagination endpoint (#2486) Version Packages (beta) (#2451) Fix Next workflow module specifier root (#2455) [world-vercel] Send remoteRefBehavior=lazy on v4 metadata-only event listings (#2415) [swc-plugin] Fix eager discovery for object property steps (#2484) fix(web-shared): align attributes panel styling (#2483) [web-shared] Auto-scroll trace viewer on J/K span navigation (#2366) fix(web): render restarted step segment as solid gray, not running stripes (#2480) fix(web-shared): use solid gray for queued trace segment (#2474) Add trace viewer span markers for hooks and attributes (#2452) test: support Vercel protection bypass secret in e2e headers (#2458) fix(core): bump payload-compression cutoff to 5.0.0-beta.18 (#2470) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> # Conflicts: # packages/core/src/runtime.ts
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
2 participants
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.
Summary
Follow-up to #2394 (payload compression), which auto-merged. The
FORMAT_VERSION_TABLEcutoff forgzip/zstdis one beta too low and would cause silent replay corruption once compression ships.The bug
#2394 gates both compression codecs on
minVersion: '5.0.0-beta.16'. But:workflow@5.0.0-beta.16— tagged 2026-06-15 (Version Packages #2390)workflow@5.0.0-beta.17— tagged 2026-06-15 (Version Packages #2428)git merge-base --is-ancestor 5f0b84521 workflow@5.0.0-beta.17reports NOT an ancestorNeither published beta contains the compression read path. The next published version is beta.18 (pending
Version Packages #2451), which is the first that can decode these payloads.With the cutoff at beta.16,
getRunCapabilities()reports a target running beta.16 or beta.17 as compression-capable. A cross-deploymentstart()/resumeHook()to such a target — or a resilient-start capability probe resolving to one — would then write zstd/gzip payloads the target cannot decode: aReferenceError-class failure at replay, silent until it bites. This is exactly theTODO(release)hazard noted on those lines, and the same cutoff-lag class of bug that hit byte-stream framing (#1853) twice.Fix
GZIPandZSTDFORMAT_VERSION_TABLEentries (and the doc-comment changelog lines) from5.0.0-beta.16→5.0.0-beta.18.No data is corrupted in the wild yet — compression doesn't activate until a published SDK writes it, i.e. beta.18 — but this must land in the same release that first enables compression.
Testing
pnpm --filter @workflow/core test→ compression suite green (34 tests)