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

GO AND RUST BUILDERS UNLOCK CUSTOM BUILD PIPELINES, SDK FACES BREAKING CHANGES

By RepoJournal · Filed · About Vercel

Vercel's Go builder now supports buildCommand and preDeployCommand, giving teams granular control over compilation, while the TypeScript SDK ships breaking changes to checks and teams endpoints that demand immediate integration review.

The Go builder [1] landed support for buildCommand and preDeployCommand, replacing hardcoded build logic with a flexible discovery system that checks $VERCEL_OUTPUT_FILE, well-known binary names, and workPath. This mirrors the flexibility already available in Node and Python builders, and arrives alongside a Rust builder enhancement [2] that now emits project manifests with framework metadata, runtime versions, and dependency trees during build. On the SDK front, @vercel/sdk 1.21.8 [3] introduces three breaking changes across checksV2.listCheckRuns(), teams.getTeams(), and teams.patchTeam() that will require integration updates. The SDK generation pipeline was unblocked [4] by manually removing orphaned sandbox-related files that the Speakeasy generator left stranded when SandboxCommand was removed from the OpenAPI spec, preventing CI failures on future runs. In flags infrastructure [5], the team hardened package.json validation to catch missing repository metadata before npm registry submission, eliminating 422 errors on sigstore provenance verification.

Action items

References

  1. [1] [go] Add support for preDeploy and buildCommand to Go. ↗ vercel/vercel
  2. [2] [services] Add project manifest to rust builder. ↗ vercel/vercel
  3. [3] typescript - v1.21.8 - 2026-05-25 22:18:51 ↗ vercel/sdk
  4. [4] fix: unblock SDK generation — remove orphaned v1 sandbox files and sync spec ↗ vercel/sdk
  5. [5] Add package.json metadata & validation script ↗ vercel/flags

FAQ

What changed in Vercel on May 26, 2026?
Vercel's Go builder now supports buildCommand and preDeployCommand, giving teams granular control over compilation, while the TypeScript SDK ships breaking changes to checks and teams endpoints that demand immediate integration review.
What should Vercel teams do about it?
Review @vercel/sdk 1.21.8 breaking changes in checksV2 and teams endpoints before next deploy • Audit Go deployments for custom build workflows and migrate to buildCommand • Monitor next.js canary 16.3.0-canary.29 for next-cache-components-optimizer behavior
Which Vercel repositories shipped on May 26, 2026?
vercel/vercel, vercel/sdk, vercel/flags

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.