This is the message we received from Cuppy in the Teable interface using ChatGPT 5.6 Sol. We are revamping a complicated app with lots of different permission and access levels. We created it a few months ago and now we are receiving the following message which is stopping us from relaunching this week: Teable must upgrade its fixed scaffold from Next.js 16.1.6 to 16.2.11 or later.
The alternative proposed was: …to move to independently controlled hosting.
And because of this: The existing security release gate would remain blocked until that external deployment passed the full release verification.
Thank you for reaching out. Please ask Cuppy to proceed with the required Next.js upgrade to version 16.2.12.
You can use the following prompt:
Please upgrade the app’s Next.js version.
The “Stack (fixed — do not propose alternatives)” rule in AGENTS.md does not apply here — package.json belongs to this app and I am authorizing this change.
Set both “next” and “eslint-config-next” to 16.2.12 in package.json.
Keep the existing pnpm overrides as they are.
Run pnpm install, then pnpm build, and confirm the build succeeds.
Do not change anything else — no other dependencies, no application code, no configuration, and nothing related to the release gate. Report the build result when done.
We will also review and handle related issues on our side.
As of now, the latest stable Next.js release is 16.3.3 (Active LTS). If your project is still on 15.x, the corresponding maintenance release is 15.5.24. The canary channel is currently on 16.4.0-canary, published daily — good for trying things out, not for production.
Next.js ships quickly, so anything we quote here can go out of date. The official sources are the ones to go by: