Merged
Conversation
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
1 participant
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.
Addresses Runtime Dependency Vulnerability mentioned in https://app.asana.com/1/137249556945/project/1199892415909552/task/1213749409399673?focus=true
Note
Medium Risk
Framework upgrade changes Next.js runtime/compiler packages and associated transitive deps, which can affect build output and routing/rendering behavior despite being a minor version bump.
Overview
Updates the app to Next.js
16.2.3(from16.1.6) and alignseslint-config-next/@next/*packages accordingly.Refreshes the lockfile with the new Next.js release and updated transitive dependencies (including
sharpand various tooling/libs) to address the reported runtime dependency vulnerability.Reviewed by Cursor Bugbot for commit 7a91a6e. Bugbot is set up for automated code reviews on this repo. Configure here.