Who contributed to Vercel on May 10, 2026?

4 developers shipped this update, including visyat, bensabic, github-actions[bot], and anthonyshew.

What were the notable Vercel updates?

Revert "feat(slack): expose direct WebClient access via adapter.client", feat(slack): expose direct WebClient access via adapter.client, and Revert "feat(slack): expose direct WebClient access via adapter.client" (#472).

May 10, 2026

$ the-wire · showcase

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

By RepoJournal · Filed 06:00 UTC on May 10, 2026 · About Vercel · Composed from the cited sources · methodology

4 people shipped this

visyat @visyat 1 cited

bensabic @bensabic 1 cited

github-actions[bot] @github-actions[bot] 1 cited

anthonyshew @anthonyshew 1 cited

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

→ Review any custom Slack API URL configs—they were silently ignored until v1 ships the fix vercel/chat [immediate]
→ Pull Next.js canary.18 in dev environments to validate CI speedups before stable release vercel/next.js [plan]
→ Monitor Turborepo v2.9.12 for versioned docs issues—release flagged aliasing failures in automation vercel/turborepo [monitor]

References

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