[vercel-gh-bot-4]

• Stale claim: "Persistent across deployments: Cached data survives new deploys". That holds for getCache entries, but not for the 'use cache: remote' path the skill recommends for Next.js 16. An agent could pick that directive expecting entries to outlive a deploy. Correction: getCache entries survive new deploys, but Next.js 16 use cache: remote entries are not readable after a new deployment. Their keys include the build ID, or the deploymentId when one is configured (for example with Skew Protection). Source: https://vercel.com/docs/caching/runtime-cache (last_updated 2026-08-28): "Next.js includes the build ID in every use cache: remote cache key, or the deploymentId when one is configured." The page's table also lists use cache: remote in Next.js 16 as "Not today" for "Readable after a new deployment". Corroborated by https://nextjs.org/docs/app/api-reference/directives/use-cache-remote: "Remote cache entries do not persist across deploys."

Verification

run_plugin_checks: build, typecheck, validate, and test all passed (1279 tests pass, 0 fail).

Test updates

None.

Not changed

• Every other claim checked out against the docs pages and @vercel/functions@3.10.4 types:
  • the getCache API, including namespaceSeparator defaulting to $, get returning null, and the name, tags, and ttl set options
  • expireTag accepting a string or an array, with 300ms global propagation
  • the purge functions
  • the CLI cache subcommands and flags
  • the limits (2 MB item size, 128 tags, 256 bytes per tag, 16 tags per bulk call)
  • the Next.js 16 revalidateTag and updateTag semantics
  • the CDN dashboard changelog

Opened automatically by the vercel-plugin drift agent. Review before merge.

---

Drift scan update 2026-11-02

• Stale claim: "Persistent across deployments: Cached data survives new deploys". The skill also recommends 'use cache: remote' as the Next.js 16 way to store data in Runtime Cache, so an agent would assume those entries survive a deploy too. They don't. Correction: getCache entries survive new deploys, but Next.js 16 'use cache: remote' entries don't. Their keys include the build ID, or the deploymentId when one is configured (for example, with Skew Protection).
  • https://vercel.com/docs/caching/runtime-cache (last_updated 2026-08-28): "Next.js includes the build ID in every use cache: remote cache key, or the deploymentId when one is configured." The deployment table on that page also lists use cache: remote in Next.js 16 as "Not today" for "Readable after a new deployment". On Skew Protection, the same page says: "On Vercel, Next.js projects with Skew Protection enabled get a deploymentId set from the deployment's ID."
  • https://nextjs.org/docs/app/api-reference/directives/use-cache-remote (lastUpdated 2026-08-18): "Remote cache entries do not persist across deploys."

Verification

run_plugin_checks passed every step: build (0 updated, 7 unchanged), typecheck, validate (PASSED, all checks OK), and test (1279 pass, 0 fail).

Test updates

None.

Not changed

• "Next.js revalidatePath / revalidateTag does NOT invalidate Runtime Cache": the @vercel/functions API reference (last_updated 2026-09-03) still says "Next.js's revalidatePath and revalidateTag APIs do not invalidate the Runtime Cache." The Runtime Cache page, though, shows revalidateTag invalidating use cache: remote data. The docs disagree with each other, so I left this line alone.
• The Data Cache move to Runtime Cache (changelog, 2026-10-30) doesn't contradict anything in the skill. vercel cache purge --type data is still in the CLI source.
• These all match the docs and CLI source: the CLI commands and flags, the getCache options ($ separator), get returning null, expireTag's 300ms propagation, the limits (2 MB, 128 tags, 256 bytes, 16 tags per bulk call), the Next.js 16 invalidation table, and the CDN dashboard and project-level routing note.

Opened automatically by the vercel-plugin drift agent. Review before merge.

---

Drift scan update 2026-11-05

• Stale claim: "Persistent across deployments: Cached data survives new deploys". The skill recommends 'use cache: remote' for Next.js 16, but those entries can't be read after a new deployment. Correction: getCache entries survive new deploys, but Next.js 16 use cache: remote keys include the build ID (or deploymentId), so a new deployment can't read them. Source: https://vercel.com/docs/caching/runtime-cache (last_updated 2026-08-28): "Next.js includes the build ID in every use cache: remote cache key, or the deploymentId when one is configured." The same page's table lists getCache as readable after a new deployment ("Yes") and use cache: remote as "Not today". Next.js agrees at https://nextjs.org/docs/app/api-reference/directives/use-cache-remote: "Remote cache entries do not persist across deploys."

Verification

run_plugin_checks: build, typecheck, validate, and test all passed (1313 tests pass, 0 fail).

Test updates

None.

Not changed

• The Data Cache to Runtime Cache migration (changelog dated 2026-10-30) doesn't contradict anything in the skill. vercel cache purge --type data and tag purges that clear CDN, Runtime Cache, and Data Cache still match https://vercel.com/docs/cli/cache and https://vercel.com/docs/caching/cdn-cache/purge.
• The getCache options, the get → null return value, the 300ms expireTag propagation, the limits table, the CLI flags, and the March 5, 2026 CDN dashboard note all match current docs and the @vercel/functions 3.10.6 types.

Opened automatically by the vercel-plugin drift agent. Review before merge.