[Chore] Update Next.js security fixes#713
Merged
Merged
Conversation
Contributor
Author
mrubens
marked this pull request as ready for review
July 23, 2026 11:08
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
July 23, 2026 11:08
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.
What changed
Why this change was made
Next.js versions before 16.2.11 are affected by the related Dependabot runtime security alerts #49 through #57. This update adopts the first patched release for that alert bundle.
Impact
The web application resolves Next.js 16.2.11, removing the vulnerable 16.2.6 resolution. The web build, repository linting, and repository type checks pass; the full web test suite has six environment-dependent failures (database/S3 timeouts and configured app URL expectations) that are unrelated to this dependency-only change.