fix(web): pin Next.js back to 16.3.5 to restore /flows and /docs (prod 500s) by khaliqgant · Pull Request #129 · AgentWorkforce/agentrelay.com

khaliqgant · 2026-10-02T06:21:20Z

Production incident

https://agentrelay.com/flows and every https://agentrelay.com/docs/<slug> page (e.g. /docs/introduction) have returned 500 Internal Server Error since #126 (Next.js 16.3.5 → 16.3.8) deployed at 2026-10-02 04:40 UTC.

This PR reverts 646f9cc. Only web/package.json and package-lock.json change, back to exactly what was deployed and healthy on 2026-10-01.

Evidence

The preview build of Upgrade Next.js to 16.3.8 #126, which contains only the version bump, returns 500 on /flows and /docs/introduction (https://8b743c8b-agentrelay-web.agent-workforce.workers.dev). So do the previews of test(flows): size the push-guard git tests' timeout to their real work #127 and Remove /chief page #128, which were built on top of it.
Under 16.3.8 every prerendered page answers with x-nextjs-cache: MISS, including pages that return 200 (/, /blog, /about). The static-assets incremental cache is no longer hit, so the Worker renders at request time. web/open-next.config.ts and the Populate static-assets cache step in deploy.yml both document that a runtime render of docs pages fails in the Workers runtime.
The same 500 is returned by origin-web.agentrelay.com directly, so the router Worker is not involved.
Upstream report of the same mechanism: Next 16.3.8: build-time prerendered entries are never read (cache handler is asked for /route-cache/<KIND>/<hash>/$<path>) opennextjs/opennextjs-aws#1269 ("Next 16.3.8: build-time prerendered entries are never read").

Not yet captured: the runtime exception from the Worker logs. The cache-miss mechanism is inferred from response headers and the upstream report.

How to verify before merging

On this PR's preview URL, both of these should return 200:

/flows
/docs/introduction

Follow-ups (not in this PR)

Do not re-attempt the 16.3.8 upgrade until the OpenNext adapter reads the new prerender cache keys.
CI and the preview workflow passed on Upgrade Next.js to 16.3.8 #126 while two top-level pages were 500ing. A post-build smoke check of a few prerendered routes on the preview would have caught it.

@khaliqgant — needs the two reviews plus a human merge to deploy.

🤖 Generated with Claude Code

Note

^{Cursor Bugbot is generating a summary for commit 186d503. Configure here.}

Summary by cubic

Pins Next.js back to 16.3.5 to restore /flows and /docs pages, which have returned 500 in production since the 16.3.8 upgrade.

With 16.3.8 the OpenNext adapter stops hitting the static-assets cache (every prerendered page answers x-nextjs-cache: MISS), so pages that can't render in the Workers runtime fail at request time. The diff is only the version pin in web/package.json and package-lock.json, reverting to the exact healthy build from 2026-10-01.

Do not retry the 16.3.8 upgrade until @opennextjs/cloudflare reads the new prerender cache keys.

^{Written for commit 186d503. Summary will update on new commits.}

Agent Relay sessions

claude session fe983435 · opened via gh pr create · last active 2026-10-02

Reverts 646f9cc (Upgrade Next.js to 16.3.8, #126). Since that upgrade deployed, /flows and every /docs/<slug> page return 500 in production. Under 16.3.8 every prerendered page reports x-nextjs-cache: MISS: the static-assets incremental cache from @opennextjs/cloudflare 1.20.1 is no longer hit, so the Worker re-renders pages at request time. Pages that cannot render in the Workers runtime (docs MDX, /flows) fail with 500; the rest only look healthy because they happen to survive a live render. The #126 PR preview, which contains nothing but the version bump, already shows the same 500s. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

chatgpt-codex-connector · 2026-10-02T06:21:25Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

coderabbitai · 2026-10-02T06:21:38Z

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 07ec3ef4-e59f-49fd-8c2b-9c8c085ff2d1

📥 Commits

Reviewing files that changed from the base of the PR and between d590f7a and 186d503.

⛔ Files ignored due to path filters (1)

package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

web/package.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

Walkthrough

The next dependency in web/package.json changes from version 16.3.8 to 16.3.5.

Changes

Web dependency update

Layer / File(s)	Summary
Update Next.js version `web/package.json`	The pinned `next` version changes from `16.3.8` to `16.3.5`.

Priority: ⬆️ High

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Bug fix

Suggested reviewers: willwashburn

Merge Risk: ⚪ Minimal · up to 186d5

No actionable merge-blocking issue is established by this review. Confirm that the preview serves /flows and /docs/introduction successfully before deployment.

Architecture Summary

Architecture risk: 🔵 Low · up to 186d5

The change affects 1 system.

Changed systems: web

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

observed — web (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

observed — Modified behavior in web/package.json: The next dependency version changes from 16.3.8 to 16.3.5.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the Next.js version rollback and the affected production routes.
Description check	✅ Passed	The description is directly related to the changes and provides incident context, evidence, verification steps, and follow-ups.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Commit to this branch
Create a new PR

Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{A rabbit checks the package pin,
And notes the version settling in.
From eight to five, the numbers hop,
One small change, then paws can stop.
The web builds onward, neat and trim.}

_{Comment @coderabbitai help to get the list of available commands.}

devin-ai-integration

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

cubic-dev-ai

No issues found across 2 files

_{Re-trigger cubic}

github-actions · 2026-10-02T06:27:24Z

Preview deployed!

Environment	URL
Web	https://ca12a1f9-agentrelay-web.agent-workforce.workers.dev

This is a Cloudflare Workers preview version of this PR's build.

devin-ai-integration Bot reviewed Oct 2, 2026

View reviewed changes

cubic-dev-ai Bot reviewed Oct 2, 2026

View reviewed changes

khaliqgant mentioned this pull request Oct 2, 2026

fix(web): restore /flows and /docs on Next 16.3.8 (fix forward, alternative to #129) #130

Merged

khaliqgant closed this Oct 2, 2026

khaliqgant deleted the fix/pin-next-16.3.5 branch October 2, 2026 06:36

Navigation Menu

Repository navigation

fix(web): pin Next.js back to 16.3.5 to restore /flows and /docs (prod 500s) - #129

fix(web): pin Next.js back to 16.3.5 to restore /flows and /docs (prod 500s)#129
khaliqgant wants to merge 1 commit into
mainfrom
fix/pin-next-16.3.5

khaliqgant commented Oct 2, 2026 •

edited by agent-relay-code Bot

Loading

Uh oh!

chatgpt-codex-connector Bot commented Oct 2, 2026

Uh oh!

coderabbitai Bot commented Oct 2, 2026 •

edited

Loading

Walkthrough

Changes

Uh oh!

devin-ai-integration Bot left a comment

Uh oh!

cubic-dev-ai Bot left a comment

Uh oh!

github-actions Bot commented Oct 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

khaliqgant commented Oct 2, 2026 • edited by agent-relay-code Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Production incident

Evidence

How to verify before merging

Follow-ups (not in this PR)

Summary by cubic

Uh oh!

chatgpt-codex-connector Bot commented Oct 2, 2026

Uh oh!

coderabbitai Bot commented Oct 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Architecture Summary

Uh oh!

devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

✅ Devin Review: No Issues Found

Uh oh!

cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Oct 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

khaliqgant commented Oct 2, 2026 •

edited by agent-relay-code Bot

Loading

coderabbitai Bot commented Oct 2, 2026 •

edited

Loading