3a31b96f26
This ensures we properly update the query when doing a shallow navigation with middleware present and expands our test coverage of this kind of navigation. This also adds middleware rewrite coverage for the case described in https://github.com/vercel/next.js/issues/38405 and ensures we properly resolve dynamic middleware rewrites which was causing https://github.com/vercel/next.js/issues/39049 Test deployment with fix can be seen [here](https://middleware-i18n-redirect-repro-8jd3x47j9-ijjk-testing.vercel.app/gsp/first) and [here](https://nextjs-middleware-rewrite-l6q20cwo3-ijjk-testing.vercel.app/) ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` Fixes: https://github.com/vercel/next.js/issues/38495 Fixes: https://github.com/vercel/next.js/issues/39049 Fixes: https://github.com/vercel/next.js/issues/38405 |
||
|---|---|---|
| .. | ||
| pages | ||
| middleware.js | ||
| next.config.js | ||