RepoJournal
Vercel

@vercel

Next.js + the Vercel platform — frontend infrastructure for the web

Pick a date

  1. Tue 5 may
  2. Wed 6 may
  3. Thu 7 may
  4. Fri 8 may
  5. Sat 9 may
  6. Sun 10 may
  7. Mon 11 may
  8. Tue 12 may
  9. Wed 13 may
  10. Thu 14 may
  11. Fri 15 may
  12. Sat 16 may
  13. Sun 17 may
  14. Mon 18 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

WORKFLOW FIXES CHUNK REORDERING BUG, NEXT.JS CLEANS UP INTERNAL SKILLS, SHOP TEMPLATES SHIP FEATURE FLAGS

By RepoJournal · Filed · About Vercel

Workflow's getWritable() memoization fix stops silent chunk reordering that was quietly corrupting output streams under load on Vercel.

The biggest story overnight: Workflow patched a critical bug [1] where calling getWritable() multiple times in the same function spawned competing TransformStreams that raced to flush to the same (runId, name) tuple. On Vercel's 50-100ms HTTP write latency, that race became deterministic corruption. Memoization stops it cold. Meanwhile, Turbopack's Windows sourcemap read crash got fixed across the entire Workflow monorepo [2], unblocking flaky E2E tests that were hitting path separator bugs in SWC worker initialization. Next.js quietly marked backport-pr and create-pr as internal metadata [3] to keep maintainer workflows out of the public skills registry in canary.28 [4]. Turborepo's profiler now traces previously invisible gaps in turbo run: remote cache resolution, preflight checks, signal handlers, and log flushing [5]. Finally, Vercel Shop shipped explicit feature flags for auth and agent [6], replacing the old implicit opt-out model with clean NEXT_PUBLIC_ENABLE_* convention, and wired every "Vercel Shop" string through siteConfig.name [7] so templates actually respect branding at deploy time.

Action items

References

  1. [1] [core] Memoize `getWritable()` to fix chunk reordering when called repeatedly ↗ vercel/workflow
  2. [2] build: use inline sourcemaps across all workspace packages ↗ vercel/workflow
  3. [3] [Skills] Mark backport-pr and create-pr as internal (#94076) vercel/next.js
  4. [4] v16.3.0-canary.28 ↗ vercel/next.js
  5. [5] fix: Improve profile tracing coverage ↗ vercel/turborepo
  6. [6] Introduce auth/agent feature flags in lib/config ↗ vercel/shop
  7. [7] [template] route storefront brand through siteConfig.name (#290) vercel/shop

FAQ

What changed in Vercel on May 24, 2026?
Workflow's getWritable() memoization fix stops silent chunk reordering that was quietly corrupting output streams under load on Vercel.
What should Vercel teams do about it?
Rebuild Workflow monorepo to pick up inline sourcemaps fix - unblocks Windows E2E • Test Workflow getWritable() in streaming scenarios to verify chunk ordering is stable • Update Shop template deployment docs - feature flags now require explicit opt-in
Which Vercel repositories shipped on May 24, 2026?
vercel/workflow, vercel/next.js, vercel/turborepo, vercel/shop

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.