RepoJournal
Vercel

@vercel

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

Pick a date

The Wire · Showcase

SLACK ADAPTER REVERTED AFTER TOKEN RESOLUTION BUG, NEXT.JS CANARY CUTS CI TIME

By RepoJournal · Filed · About Vercel

Vercel/Chat pulled the Slack direct WebClient access feature after discovering it silently dropped custom API URLs, while Next.js canary lands 41-second CI wins across test workflows.

The Slack adapter revert [1] undoes a feature that exposed the underlying @slack/web-api WebClient for direct API calls [2], but the implementation had a critical flaw: `createSlackAdapter()` was dropping the `apiUrl` config field entirely, breaking GovSlack and other custom Slack deployments [3]. This is a good catch—the pattern mirrors Linear and GitHub adapters, but shipping broken config handling is worse than shipping nothing. Meanwhile, Next.js canary.18 [4] landed incremental wins: restored pnpm store caching and eliminated redundant Playwright installs across steps [5], cutting 41 seconds from CI pipelines that don't need browser testing. The core changes also remove redundant instant navigation prefetch headers [4] and improve error reporting in Instant Insights. Over in Turborepo, the team shipped v2.9.12 [6] while quietly restoring the mobile docs menu that broke navigation on narrow widths [7]. Vercel's CLI and build packages all bumped with dependency updates [8][9][10][11][12]—nothing earth-shattering, but Python tooling gained service type metadata in the project manifest [12]. Workflow SDK cleaned up the instrumentation stub in the workbench [13], aligning testing with actual getting-started guidance.

Action items

References

  1. [1] Revert "feat(slack): expose direct WebClient access via adapter.client" ↗ vercel/chat
  2. [2] feat(slack): expose direct WebClient access via adapter.client ↗ vercel/chat
  3. [3] Revert "feat(slack): expose direct WebClient access via adapter.client" (#472) vercel/chat
  4. [4] v16.3.0-canary.18 ↗ vercel/next.js
  5. [5] CI speed improvements (#93411) vercel/next.js
  6. [6] release(turborepo): 2.9.12 ↗ vercel/turborepo
  7. [7] fix: Restore docs mobile menu ↗ vercel/turborepo
  8. [8] @vercel/[email protected] vercel/vercel
  9. [9] @vercel/[email protected] vercel/vercel
  10. [10] [email protected] vercel/vercel
  11. [11] @vercel/[email protected] vercel/vercel
  12. [12] @vercel/[email protected] vercel/vercel
  13. [13] Remove instrumentation from workbench (#1959) vercel/workflow

FAQ

What changed in Vercel on May 10, 2026?
Vercel/Chat pulled the Slack direct WebClient access feature after discovering it silently dropped custom API URLs, while Next.js canary lands 41-second CI wins across test workflows.
What should Vercel teams do about it?
Review any custom Slack API URL configs—they were silently ignored until v1 ships the fix • Pull Next.js canary.18 in dev environments to validate CI speedups before stable release • Monitor Turborepo v2.9.12 for versioned docs issues—release flagged aliasing failures in automation
Which Vercel repositories shipped on May 10, 2026?
vercel/chat, vercel/next.js, vercel/turborepo, vercel/vercel, 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.