115 wires and counting

$ follow Vercel

Keep up with Vercel in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-09-06
stories 17

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Uncapped chat history retention, dev overlay route overrides fixed

By RepoJournal · Filed · About Vercel

Vercel's chat library now supports unlimited per-user history retention, and Next.js fixes stale route info in the dev overlay.

The vercel/chat history feature now accepts `history.user.maxPerUser: false` and the legacy `transcripts.maxPerUser: false` to disable count-based eviction, so apps can retain complete user histories beyond the default 200 entries [1]. Numeric limits still trim older entries, and retention TTL remains independent. Tests cover retaining 205 entries with no cap, the default 200-entry cap, and legacy configuration merging [2].

Next.js fixed an issue in the Route Info dev tools panel where toggling a route segment boundary like `loading.js` or `not-found.js` didn't update the UI until the modal was closed and reopened [3]. The cause was the segment explorer trie mutating nodes in place, which prevented the memoized view from picking up insertions until remount [4].

The AI SDK @ai-sdk/openai 4.0.60 adds "GPT-6 reasoning configuration updates" [5], with @ai-sdk/azure 4.0.63 and @ai-sdk/amazon-bedrock 5.0.76 updating their OpenAI dependency accordingly [6][8]. These are patch releases with no breaking changes.

Action items

References

  1. [1] feat(history): support uncapped per-user retention ↗ vercel/chat
  2. [2] feat(history): support uncapped per-user retention (#904) ↗ vercel/chat
  3. [3] fix: route info segment overrides not updating in dev overlay ↗ vercel/next.js
  4. [4] fix: route info segment overrides not updating in dev overlay (#96968) ↗ vercel/next.js
  5. [5] v16.4.0-canary.19 ↗ vercel/next.js
  6. [6] @ai-sdk/openai@4.0.60 ↗ vercel/ai
  7. [7] @ai-sdk/azure@4.0.63 ↗ vercel/ai
  8. [8] @ai-sdk/amazon-bedrock@5.0.76 ↗ vercel/ai

Quick answers

What shipped in Vercel on September 6, 2026?
Vercel's chat library now supports unlimited per-user history retention, and Next.js fixes stale route info in the dev overlay. In total, 4 commits, 4 pull requests, and 9 releases landed.
Who contributed to Vercel on September 6, 2026?
4 developers shipped this update, including onmax, mezotv, next-js-bot[bot], and github-actions[bot].
What were the notable Vercel updates?
feat(history): support uncapped per-user retention, feat(history): support uncapped per-user retention (#904), and fix: route info segment overrides not updating in dev overlay.