Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix `generateBuildId` in `next.config.ts` not respected in v16.2.0+ [1 pull requests, 9 comments, 7 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#92154•Fetched 2026-04-08 01:56:46
View on GitHub
Comments
9
Participants
7
Timeline
27
Reactions
4
Author
stayko-chalakovstayko-chalakov
Participants
christopherjohnson3028-stackchristopherjohnson3028-stackharry-gocityharry-gocitykiilykiilymischnicmischnicstayko-chalakovstayko-chalakovvictorlangston123-droidvictorlangston123-droidZvanderschyffZvanderschyff
Timeline (top)
commented ×9subscribed ×7mentioned ×5renamed ×4

PR fix notes

PR #4574: enable turbopack, enable version skew configs and remove version checker

Description (problem / solution / changelog)

closes #4565, closes #3961

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

Summary by CodeRabbit

Release Notes

  • Refactor

    • Removed automatic version checking and update notifications that previously prompted users to refresh the app when new versions were deployed.
    • Optimized build configuration for improved performance using updated bundling tools.

  • Chores

    • Enhanced deployment workflows with improved build process handling and environment variable management.
    • Updated Docker build pipeline for better consistency across deployment environments.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Changed files

  • .github/workflows/docker_build.yml (modified, +8/-0)
  • .github/workflows/pr_preview.yml (modified, +1/-0)
  • Dockerfile (modified, +9/-2)
  • front_end/next.config.mjs (modified, +31/-50)
  • front_end/package.json (modified, +1/-1)
  • front_end/src/app/(api)/app-version/route.ts (removed, +0/-8)
  • front_end/src/app/(futureeval)/futureeval/layout.tsx (modified, +0/-2)
  • front_end/src/app/(main)/components/version_checker.tsx (removed, +0/-111)
  • front_end/src/app/(main)/layout.tsx (modified, +0/-2)
  • front_end/src/app/(storefront)/layout.tsx (modified, +0/-2)
  • front_end/src/proxy.ts (modified, +1/-1)
  • front_end/src/sentry/options.ts (modified, +0/-5)

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:45 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 23.11.0
  npm: 11.6.3
  Yarn: 1.22.22
  pnpm: 8.15.5
Relevant Packages:
  next: 16.1.7 // There is a newer version (16.2.1) available, upgrade recommended!
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A
⚠ There is a newer version (16.2.1) available, upgrade recommended!
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/stayko-chalakov/build-id-issue-16.2

To Reproduce

  1. npm install
  2. npm run build
  3. npm run start
  4. Go to localhost:3000 and open the Network tab in your browser's dev tools
  5. Refresh the page
  6. Type build- in the filter input in Network tab and observe the requests to _/next/static and _next/data with build-TfctsWXpff2fKS

Current vs. Expected behavior

Current (16.2.0 or 16.2.1 or canary):

<img width="1207" height="168" alt="Image" src="https://github.com/user-attachments/assets/f8f452a7-e285-4c96-b33e-fa8dc8f030c4" />

Expected (before 16.2.0, e.g 16.1.7):

<img width="1206" height="185" alt="Image" src="https://github.com/user-attachments/assets/3ee73e4d-60a4-429c-accc-15a9d6c05d4d" />

generateBuildId here is not being respected: https://github.com/stayko-chalakov/build-id-issue-16.2/blob/b5ef22c929995fbc383aaca8ae8744f23ccecd81/next.config.ts#L7

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:45 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 23.11.0
  npm: 11.6.3
  Yarn: 1.22.22
  pnpm: 8.15.5
Relevant Packages:
  next: 16.1.7 // There is a newer version (16.2.1) available, upgrade recommended!
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A
⚠ There is a newer version (16.2.1) available, upgrade recommended!
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next start (local)

Additional context

No response

extent analysis

TL;DR

  • The issue with generateBuildId not being respected in Next.js version 16.2.0 or 16.2.1 may be resolved by upgrading to the latest canary version.

Guidance

  • Try upgrading to the latest canary version of Next.js by running npm install next@canary to confirm if the issue still exists.
  • Verify that the generateBuildId function is correctly configured in the next.config.ts file.
  • Check the documentation for any changes to the generateBuildId function in version 16.2.0 or 16.2.1.
  • If the issue persists, try downgrading to version 16.1.7 to see if the issue is specific to version 16.2.0 or 16.2.1.

Example

  • No code snippet is provided as the issue is related to configuration and versioning.

Notes

  • The issue may be specific to the version of Next.js being used, and upgrading or downgrading may resolve the issue.
  • The generateBuildId function is not a standard function in Next.js, so it's possible that it's a custom function that's not being respected in the latest versions.

Recommendation

  • Apply workaround: Upgrade to the latest canary version of Next.js to see if the issue is resolved, as the current version may have a bug that's causing the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#prompt template#agent execution#callback error#memory management#API rate limit

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING