fix(deps): bump next to 16.2.12 to close 28 advisories - #57
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Bumps
nextfrom 16.1.6 to 16.2.12, closing every open Dependabot advisory on the repo.What this fixes
All 28 open alerts were the same package —
next— and all are fixed in ≥ 16.2.6. 16.2.12 is the latest 16.x, so this takes the remaining patches too.The 12 highs are server-side request forgery, middleware/proxy bypass, and denial of service. Those matter because intentface.dev is publicly reachable, so they aren't theoretical for the deployed site.
It does not affect the published package
Worth stating precisely, since it's the obvious worry:
nextappears nowhere inpackages/chat/package.json, and nothing underpackages/chat/srcorpackages/chat/testsimports itpackage.json; zero were inpackages/chat@intentface/chat@0.1.0ships two runtime deps —@floating-ui/domandnanoid— neither of which has an advisoryAnd rather than reason about it, I compared the built artifact across the bump:
142 files, byte-for-byte unchanged. The bump cannot alter what consumers install.
Verified
179 tests,
tsc --noEmitclean, biome clean, publint clean, and the app builds all 21 routes with the same route shape as before.No changeset: the published package is untouched, so there is nothing to release.