Repository navigation
fix(security): upgrade Next.js to 16.2.6 and migrate middleware to proxy - #25
Merged
Merged
Conversation
josego85
commented
May 16, 2026
josego85
commented
Owner
- Bumps next from 16.2.3 → 16.2.6 to patch 13 high-severity CVEs (cache poisoning, middleware/proxy bypasses, DoS, XSS)
- Renames src/middleware.ts → src/proxy.ts following the Next.js 16 deprecation of the "middleware" file convention in favour of "proxy"
- Build and lint pass clean with Node.js 22 after the migration
- Bumps next from 16.2.3 → 16.2.6 to patch 13 high-severity CVEs (cache poisoning, middleware/proxy bypasses, DoS, XSS) - Renames src/middleware.ts → src/proxy.ts following the Next.js 16 deprecation of the "middleware" file convention in favour of "proxy" - Build and lint pass clean with Node.js 22 after the migration
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.