{"id":"org_qsyZSlC_PRGFDYIGsMfzp","slug":"vercel","name":"Vercel","domain":"vercel.com","description":null,"category":"cloud","tags":["typescript"],"sourceCount":6,"releaseCount":2576,"releasesLast30Days":1959,"avgReleasesPerWeek":185.7,"lastFetchedAt":"2026-04-19T03:01:40.738Z","trackingSince":"2019-10-29T18:59:22.000Z","aliases":[],"accounts":[{"platform":"github","handle":"vercel"},{"platform":"x","handle":"vercel"}],"products":[{"id":"prod_JoRuQm6EnVccYeDh_NTEz","slug":"nextjs","name":"Next.js","url":"https://nextjs.org","description":"React framework for production","sourceCount":1},{"id":"prod_AYklyECIj-XY2rdp8m6bq","slug":"turborepo","name":"Turborepo","url":"https://turbo.build","description":null,"sourceCount":1}],"sources":[{"id":"src_euVMpVWtHmJQBzLinVJhu","slug":"vercel-ai-sdk","name":"AI SDK","type":"github","url":"https://github.com/vercel/ai","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":1514,"latestVersion":"@ai-sdk/openai-compatible@3.0.0-beta.31","latestDate":"2026-04-17T22:11:47.000Z","latestAddedAt":"2026-04-18T01:00:44.741Z","productSlug":null,"productName":null},{"id":"src_U4D8mfwIxWDEaM4qDm3Lq","slug":"next-js","name":"Next.js","type":"github","url":"https://github.com/vercel/next.js","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":237,"latestVersion":"v16.3.0-canary.2","latestDate":"2026-04-18T23:44:17.000Z","latestAddedAt":"2026-04-19T03:01:36.789Z","productSlug":"nextjs","productName":"Next.js"},{"id":"src_ywQzOi8KdZ7iAS8fLDE-O","slug":"swr","name":"SWR","type":"github","url":"https://github.com/vercel/swr","isPrimary":false,"isHidden":false,"fetchPriority":"low","releaseCount":126,"latestVersion":"v2.4.0","latestDate":"2026-02-01T03:02:37.000Z","latestAddedAt":"2026-04-18T13:09:41.944Z","productSlug":null,"productName":null},{"id":"src_hy53FJP-EvU5bXwaAlBp_","slug":"turborepo","name":"Turborepo","type":"github","url":"https://github.com/vercel/turborepo","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":238,"latestVersion":"v2.9.7-canary.13","latestDate":"2026-04-16T16:41:11.000Z","latestAddedAt":"2026-04-16T20:03:35.470Z","productSlug":"turborepo","productName":"Turborepo"},{"id":"src_ybwLQLQFrJY-rVJQeGetN","slug":"vercel","name":"Vercel","type":"scrape","url":"https://vercel.com/changelog","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":15,"latestVersion":null,"latestDate":"2026-04-16T00:00:00.000Z","latestAddedAt":"2026-04-16T15:06:58.720Z","productSlug":null,"productName":null},{"id":"src_zc8ffQLs3AUrXjimt4Ant","slug":"vercel-cli","name":"Vercel CLI","type":"github","url":"https://github.com/vercel/vercel","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":446,"latestVersion":"@vercel/python@6.35.0","latestDate":"2026-04-17T22:38:49.000Z","latestAddedAt":"2026-04-18T01:00:43.672Z","productSlug":null,"productName":null}],"overview":{"scope":"org","content":"**Vercel CLI gains deploy hooks and connex integration management.**\n\nThe Vercel CLI now supports `vercel deploy-hooks` for creating, listing, and removing deployment webhooks, and adds `vercel connex create` for managing integrations. The `vercel metrics` command graduated from beta, simplifying metric selection and output. Python runtime fixed non-web service route handling, and Rust runtime now supports entry points without file extensions in the dev server.\n\n**Next.js canary refines build configuration and toolchain.**\n\nThe v16.2.1-canary build allows overriding `outputHashSalt` in `modifyConfig` hooks, giving developers finer control over build artifact naming. Turbopack switched back to `lld` linker on ARM64 glibc Linux and optimized cache behavior for transform plugins.\n\n**Turborepo maintains Vercel auth compatibility.**\n\nA canary patch preserved legacy Vercel authentication flows, ensuring existing deployments continue working.\n\n**AI SDK refactored tool execution across 45+ provider integrations.**\n\nThe core `ai` package (v7.0.0-beta.100) changed how tools are passed to `executeTool`, shifting from a context-based approach to a parameter-based one. This cascaded across all provider integrations—OpenAI, Anthropic, Google, Mistral, Groq, Cohere, and 30+ others—all updated in lock-step. Framework packages (`@ai-sdk/react`, `@ai-sdk/svelte`, `@ai-sdk/vue`) and specialized modules (`@ai-sdk/rsc`, `@ai-sdk/mcp`, `@ai-sdk/workflow`) followed. The change simplifies internal APIs; no breaking changes to public surfaces are evident yet, but the scale of this refactor signals internal consolidation ahead of a 7.0 stable release.","releaseCount":2100,"lastContributingReleaseAt":"2026-04-16T13:41:59.000Z","generatedAt":"2026-04-16T15:07:30.469Z","updatedAt":"2026-04-16T15:07:30.469Z"},"knowledgePage":{"scope":"org","content":"**Vercel CLI gains deploy hooks and connex integration management.**\n\nThe Vercel CLI now supports `vercel deploy-hooks` for creating, listing, and removing deployment webhooks, and adds `vercel connex create` for managing integrations. The `vercel metrics` command graduated from beta, simplifying metric selection and output. Python runtime fixed non-web service route handling, and Rust runtime now supports entry points without file extensions in the dev server.\n\n**Next.js canary refines build configuration and toolchain.**\n\nThe v16.2.1-canary build allows overriding `outputHashSalt` in `modifyConfig` hooks, giving developers finer control over build artifact naming. Turbopack switched back to `lld` linker on ARM64 glibc Linux and optimized cache behavior for transform plugins.\n\n**Turborepo maintains Vercel auth compatibility.**\n\nA canary patch preserved legacy Vercel authentication flows, ensuring existing deployments continue working.\n\n**AI SDK refactored tool execution across 45+ provider integrations.**\n\nThe core `ai` package (v7.0.0-beta.100) changed how tools are passed to `executeTool`, shifting from a context-based approach to a parameter-based one. This cascaded across all provider integrations—OpenAI, Anthropic, Google, Mistral, Groq, Cohere, and 30+ others—all updated in lock-step. Framework packages (`@ai-sdk/react`, `@ai-sdk/svelte`, `@ai-sdk/vue`) and specialized modules (`@ai-sdk/rsc`, `@ai-sdk/mcp`, `@ai-sdk/workflow`) followed. The change simplifies internal APIs; no breaking changes to public surfaces are evident yet, but the scale of this refactor signals internal consolidation ahead of a 7.0 stable release.","releaseCount":2100,"lastContributingReleaseAt":"2026-04-16T13:41:59.000Z","generatedAt":"2026-04-16T15:07:30.469Z","updatedAt":"2026-04-16T15:07:30.469Z"},"playbook":{"scope":"playbook","content":"# Vercel — Playbook\n\n> Agent reference for fetching and maintaining **Vercel** (`vercel`) changelog sources.\n\n**6** active sources · **2** products: Next.js, Turborepo · domain: vercel.com\n\n## Sources\n\n| Name | ID | Type | URL | Product | Last Fetched |\n|------|-----|------|-----|---------|--------------|\n| Vercel | `src_ybwLQLQFrJY-rVJQeGetN` | scrape | https://vercel.com/changelog | — | Apr 16 |\n| AI SDK | `src_euVMpVWtHmJQBzLinVJhu` | github | https://github.com/vercel/ai | — | Apr 18 |\n| SWR | `src_ywQzOi8KdZ7iAS8fLDE-O` | github · low | https://github.com/vercel/swr | — | Apr 18 |\n| Vercel CLI | `src_zc8ffQLs3AUrXjimt4Ant` | github | https://github.com/vercel/vercel | — | Apr 18 |\n| Next.js | `src_U4D8mfwIxWDEaM4qDm3Lq` | github | https://github.com/vercel/next.js | Next.js | Apr 18 |\n| Turborepo | `src_hy53FJP-EvU5bXwaAlBp_` | github | https://github.com/vercel/turborepo | Turborepo | Apr 18 |\n\n## Agent Notes\n\n### Fetch instructions\n\n**Next.js** (`next-js`) — GitHub releases from `vercel/next.js`. Use `--max 50` for routine fetches; default hits the 100-entry cap on every run since this repo ships daily canary builds. Versions are semver with canary and patch tracks running in parallel (e.g., `v16.2.1-canary.32`, `v16.2.3`, `v15.5.15`). Expect 10–15 new entries per day across both tracks. All content is substantive — changelogs list PR-level changes and credits. Maps to the **Next.js** product (`nextjs`).\n\n**Turborepo** (`turborepo`) — GitHub releases from `vercel/turborepo`. Semver with parallel canary and stable tracks (e.g., `v2.9.7-canary.2`, `v2.9.6`). Expect ~24 releases/week. Canary releases frequently have empty content bodies — only a \"Full Changelog\" diff link, no bullet points. Stable releases always include a structured \"What's Changed\" breakdown. Maps to the **Turborepo** product (`turborepo`).\n\n**SWR** (`swr`) — GitHub releases from `vercel/swr`. Semver (e.g., `v2.4.0`, `v2.3.8`). This source is effectively dormant — 0 releases in the last 30 days, last release was February 2026. Skip on routine fetches unless checking for a new release. Org-level source (no product).\n\n**Vercel AI SDK** (`vercel-ai-sdk`) — GitHub releases from `vercel/ai`. This is a high-volume monorepo: scoped packages publish independently, so a single upstream change triggers multiple tagged releases (e.g., `@ai-sdk/google@3.0.62`, `@ai-sdk/anthropic@3.0.69`, `@ai-sdk/google-vertex@4.0.108`). Fetches return 100 entries nearly every run with 344 releases/week. Use `--max 100` and expect to insert 10–96 new entries per fetch. Both stable and beta tracks coexist (e.g., `ai@7.0.0-beta.83` alongside `@ai-sdk/anthropic@3.0.69` stable). Org-level source.\n\n**Vercel CLI** (`vercel-cli`) — GitHub releases from `vercel/vercel` (the repo slug is `vercel`, not `vercel-cli`). Another monorepo: releases are scoped packages (e.g., `@vercel/config@0.1.1`, `@vercel/build-utils@13.14.2`, `@vercel/client@17.3.1`). ~62 releases/week. The `vercel` CLI package itself is one of many in this repo. Use `--max 50` for routine fetches. Org-level source.\n\n**Vercel Platform** (`vercel`) — Scrape source from `vercel.com/changelog`. Set `version=null` for every release — entries are titled by event, not versioned (e.g., \"Axios package compromise and remediation steps\", \"Vercel CDN now respects cache-control headers\"). JS-rendered SPA; no RSS feed exists (`noFeedFound` in metadata). Has not been fetched since 2026-03-31 and has no cron poll records — trigger manually with `fetch vercel`. Expect ~3 entries/week when active. Org-level source.\n\n### Traps\n\n- **next-js always at cap**: Every fetch returns exactly 100 results. Without `--max`, bulk backfill pulls only 100 entries. Use `--max 50` for incremental and `--max 200+` only for initial backfill.\n- **Turborepo canary content is empty**: Many canary entries contain only \"Full Changelog: ...compare/...\" with no bullet points. This is expected upstream behavior, not an extraction failure.\n- **vercel-ai-sdk volume explosion**: A single provider update triggers 3–10 tagged releases across dependent packages the same minute. This is normal fan-out from Changesets. Expect bursts, not errors.\n- **vercel-cli repo name mismatch**: The source slug is `vercel-cli` but the GitHub repo is `vercel/vercel`. Don't confuse it with the platform changelog source (slug `vercel`, URL `vercel.com/changelog`).\n- **vercel scrape is stale**: The platform changelog (`vercel`) has no poll record and was last fetched 2026-03-31. It requires a manual `fetch vercel` — the cron does not pick it up automatically.\n- **SWR is dormant**: Do not prioritize `swr` for routine fetches. Check quarterly or when a new release is announced externally.\n\n### Coverage\n\nFive GitHub sources cover Vercel's active open-source output; the sixth scrape source captures platform changelog entries that don't appear in any repo. The main gap is that `vercel/vercel` (CLI) is a monorepo and the `vercel` CLI package releases are buried among dozens of internal `@vercel/*` package releases — there is no separate CLI-only source.\n","updatedAt":"2026-04-18T20:41:21.664Z"}}