nextjs - ✅(Solved) Fix existing rewrite broken after version update from 15.5.6 and 16.0.0 [1 pull requests, 1 comments, 2 participants]

nextjs2025-11-21 16:00:31

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

vercel/next.js#86385•Fetched 2026-04-08 02:11:17

View on GitHub

Comments

Participants

Timeline

Reactions

Author

gabrielmfern

Participants

dzienisz

gabrielmfern

Timeline (top)

commented ×1cross-referenced ×1issue_type_added ×1labeled ×1

Code Example

bun dev

---

Binaries:
  node: 24.0.2
Relevant packages:
  next: 16.0.3

RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/gabrielmfern/rewrite-broken-in-version-update

To Reproduce

Run dev server
```
bun dev
```
Open http://localhost:3000
Click the link and see that there's no navigation

Current vs. Expected behavior

I would expect navigation to properly work and navigate to /docs instead of doing nothing.

Provide environment information

Binaries:
  node: 24.0.2
Relevant packages:
  next: 16.0.3

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

Redirects

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

Vercel (Deployed), next start (local), next build (local), next dev (local)

Additional context

I was able to narrow the issue down to 15.6.0-canary.48 onwards, with 15.6.0-canary.47 working just fine.

extent analysis

TL;DR

The issue can likely be resolved by downgrading the Next.js version to a stable release before 15.6.0-canary.48, as the problem seems to be introduced in this version.

Guidance

Verify the issue by testing with 15.6.0-canary.47 to confirm that it's indeed a regression introduced after this version.
Check the release notes and changelogs of Next.js versions after 15.6.0-canary.47 to see if there are any known issues or breaking changes related to redirects.
Test the application with a stable version of Next.js (e.g., 15.5.x) to see if the navigation works as expected.
If downgrading is not feasible, consider opening an issue on the Next.js GitHub repository to report the bug and ask for assistance.

Example

No code snippet is provided as the issue seems to be related to a specific version of Next.js rather than a code-specific problem.

Notes

The solution assumes that the issue is indeed caused by a regression in Next.js and not by a change in the application code.
Downgrading Next.js might introduce other compatibility issues, so it's essential to test the application thoroughly after making this change.

Recommendation

Apply workaround: Downgrade Next.js to a version before 15.6.0-canary.48 (e.g., 15.6.0-canary.47 or a stable 15.5.x release) to avoid the regression until a fixed version is available.

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?

#inference speed #output truncation #response parsing #generation error #database connection

Still need to ship something?

×6

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

nextjs - ✅(Solved) Fix existing rewrite broken after version update from 15.5.6 and 16.0.0 [1 pull requests, 1 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Fix Action

Fixed

PR fix notes

PR #1594: MDZ-1577: New CRM Field Account Closing Date

Description (problem / solution / changelog)

Midaz Pull Request Checklist

Pull Request Type

Checklist

Obs: Please, always remember to target your PR to develop branch instead of main.

Additional Notes

Summary by CodeRabbit

Changed files