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

TURBOREPO FIXES PNPM LOCKFILE BREAKAGE, ADDS HEAP PROFILING

By RepoJournal · Filed · About Vercel

Turborepo 2.9 now preserves pnpm injected peer dependencies during prune operations, fixing a critical lockfile corruption bug that broke frozen installs in Docker builds.

The pnpm fix [1] addresses a silent failure where turbo prune would drop base package entries needed to resolve peer-variant snapshot keys, leaving pruned lockfiles unable to install with --frozen-lockfile. This one's especially dangerous because it only surfaces at deploy time. In parallel, heap allocation profiling [2] shipped opt-in DHAT support to the Rust CLI, giving you a repeatable way to find and validate memory hotspots without custom instrumentation. The profiler outputs raw JSON plus ranked summaries by bytes and allocation count. On the observability front, OTel duration histograms got Turborepo-specific bucket boundaries [3] that actually cover real build durations instead of maxing out at 10 seconds, making P50/P95 queries and Grafana heatmaps usable again.

Action items

References

  1. [1] fix: Preserve pnpm injected peer package entries ↗ vercel/turborepo
  2. [2] feat: Add heap allocation profiling ↗ vercel/turborepo
  3. [3] fix: Use build-scale OTel duration buckets ↗ vercel/turborepo

FAQ

What changed in Vercel on May 25, 2026?
Turborepo 2.9 now preserves pnpm injected peer dependencies during prune operations, fixing a critical lockfile corruption bug that broke frozen installs in Docker builds.
What should Vercel teams do about it?
Upgrade turborepo to 2.9.15+ before next Docker build if using pnpm with workspace dependencies • Test heap profiling with --heap flag on your next optimization pass • Monitor OTel duration metrics for improved observability across your CI pipelines
Which Vercel repositories shipped on May 25, 2026?
vercel/turborepo

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.