Next.js 16 build succeeds, but @vercel/next builder rejects deployment

Help
1

Hi,

I’m seeing a consistent deployment issue where my Next.js 16 project builds successfully on Vercel, but the deployment fails after the build step with an @vercel/next error.

Key points:

  • pnpm run build (which runs bash scripts/quiet-build.sh → next build) completes successfully both locally and in Vercel.

  • The Vercel build log shows Next.js 16.0.1 detected, the app compiled, and my postbuild script executed without errors.

  • Immediately after the postbuild script finishes, the deployment fails with:

Error: This version of @vercel/next does not support the version of Next.js you are trying to deploy.
Please upgrade your @vercel/next builder and try again. Contact support if this continues to happen.

However, I am not using @vercel/next directly in my package.json – this seems to be coming from the internal builder that wraps the Next build output.

Here is the relevant tail of the failing build log (02:21 UTC):

Detected Next.js version: 16.0.1
Running "corepack enable && corepack prepare pnpm@10.0.0 --activate && pnpm run build"

> duartec-web@1.0.0 prebuild /vercel/path1
> node scripts/prebuild.mjs
[...]
> duartec-web@1.0.0 build /vercel/path1
> bash scripts/quiet-build.sh
[...]
▲ Next.js 16.0.1 (webpack, Cache Components)
✓ Compiled successfully in 45s
[...]
✅ Build limpio completado. Resumen guardado en build-summary.txt

> duartec-web@1.0.0 postbuild /vercel/path1
> node scripts/postbuild.mjs
[postbuild] Skipping next-sitemap CLI. The App Router metadata route (app/sitemap.ts) now generates sitemap.xml.
[postbuild] Scheduled late hydration for Vercel functions.
[postbuild] Vercel build detected. Skipping manual .next replication (handled by platform).
[postbuild] BUILD_ID not found — skipping function hydration.
Error: This version of `@vercel/next` does not support the version of Next.js you are trying to deploy.
Please upgrade your `@vercel/next` builder and try again. Contact support if this continues to happen.

In an earlier deployment (about an hour before), the same codebase with next@16.0.1 built and deployed successfully on Vercel: the logs showed Build Completed in /vercel/output and Deployment completed. The only changes between the successful and failing builds are minor dependency updates (e.g. next-auth, sanitize-html) and some postbuild adjustments; the Next.js version remains 16.0.1 and the app still compiles correctly.

This suggests the failure is happening in the @vercel/next builder step, not in the Next.js build itself.

Questions / Request:

  • Can you confirm which version of @vercel/next is currently being used for this project, and whether it officially supports Next.js 16.0.1?

  • If not, can you update/enable the appropriate builder for this project so that Next 16 deployments are accepted, given that the build step is already succeeding?

Happy to provide the full build logs or project ID if needed.

Thank you!

1 Like
5

Hi, can you confirm if your project is set to use the Next.js preset?

If you are manually configuring your functions/builds in the vercel.json, that could cause it to use a pinned version of the builder instead of updating automatically to the latest. Removing those keys if possible will prevent similar issues

{
  "functions": …,
  "builds": [
    { "src": "package.json", "use": "@vercel/next@latest" }
  ]
}

If that doesn’t work, can you try updating your quiet-build.sh script to run vercel build instead of next build?

1 Like
7

Hi @ia-7011, just checking in to see if you were able to resolve the deployment issue with your Next.js 16 project or if you still need assistance. Let me know how it’s going!

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.