RepoJournal
Vercel

@vercel

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

Pick a date

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

The Wire · Showcase

WORKFLOW FIXES SILENT STEP RE-EXECUTION, EVE LOCKS DOWN EXPERIMENTAL API

By RepoJournal · Filed · About Vercel

Vercel workflow shipped critical fixes preventing duplicate step execution on transient failures, while Eve removed its experimental Workflow opt-in from the public API to prevent confusion.

The workflow team landed four production hardening changes that address cascading failure modes in turbo and standard modes. The most critical: step completion POSTs that fail now retry in-process [6], preventing silent re-execution when the network hiccups but the user code already succeeded. A second fix gates fire-and-forget hook creation on the run-ready barrier [5], ensuring optimistic workflow execution doesn't leak uncommitted events. Transport failures during attacks now redrive instead of permanently failing runs [4], and all five HTTP paths through world-vercel now route through a unified core [7] with consistent observability and error handling. On the platform side, Eve 0.17.0 removed the `ExperimentalWorkflow` opt-in marker from the public `eve/tools` export [1], moving workflow tooling entirely experimental after the public API made it look production-ready. Vercel CLI 54.18.2 and fs-detectors 6.11.2 shipped a fix allowing Services v2 entries with only a `root` field to fall back to static builds [2], unblocking simplified service configs. Next.js canary gained 128-bit hash support in Turbopack [3], aligning hash operations across the build system.

Action items

References

  1. [1] [email protected] ↗ vercel/eve
  2. [2] @vercel/[email protected] ↗ vercel/vercel
  3. [3] Turbopack: make hash_xxh3_hash128 return u128 ↗ vercel/next.js
  4. [4] Redrive on transient workflow-server transport failures instead of failing the run ↗ vercel/workflow
  5. [5] [core] Gate turbo end-of-run drain writes on the run-ready barrier ↗ vercel/workflow
  6. [6] fix(world-vercel): retry idempotent event POSTs in-process to avoid step re-execution ↗ vercel/workflow
  7. [7] [world-vercel] Unify HTTP request handling into a shared core ↗ vercel/workflow

FAQ

What changed in Vercel on June 29, 2026?
Vercel workflow shipped critical fixes preventing duplicate step execution on transient failures, while Eve removed its experimental Workflow opt-in from the public API to prevent confusion.
What should Vercel teams do about it?
If you deploy workflows with fire-and-forget hooks or synchronous returns, upgrade to the latest workflow packages immediately • Remove any `ExperimentalWorkflow` imports from your Eve tools if you're on a pre-0.17 build • Upgrade Vercel CLI to 54.18.2 if deploying Services v2 with static-only roots
Which Vercel repositories shipped on June 29, 2026?
vercel/eve, vercel/vercel, vercel/next.js, vercel/workflow

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.