fix(deps): clear open Dependabot security advisories - #156
Merged
Conversation
Bump next 16.2.10 -> 16.3.1 and raise the postcss override floor to ^8.5.23, then refresh the lockfile so every flagged transitive dep lands on a patched release: fast-uri 3.1.5, ip-address 10.5.0, @hono/node-server 1.19.17, hono 4.13.2, mermaid 11.16.1, dompurify 3.4.13, nanoid 3.3.18, js-yaml 4.3.1, brace-expansion 1.1.18, postcss 8.5.26. next@16.3.1 also dedupes its bundled sharp up to the patched 0.35.3.
|
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.
Clears the open Dependabot security alerts in one consolidated lockfile refresh, rather than merging the ~9 individual bump PRs and fighting the lockfile-conflict cascade.
Heads-up on why
npm auditalone wasn't enough here: npm's advisory DB lags GitHub's for these (mostly 2026-dated) advisories, sonpm auditon main only saw next/postcss/sharp. The lockfile actually still carried the old vulnerable versions of everything else — so this bumps each one explicitly and verifies it against the GitHub-patched version, not justnpm audit.What changed
next16.2.10 → 16.3.1 — clears the App Router / Server Actions SSRF + DoS + cache-confusion advisories, and dedupes next's bundledsharpup to the patched 0.35.3 (no override needed).overrides.postcssfloor → ^8.5.23 (resolves to 8.5.26) — source-map path-traversal.memo()cross-user leak!!omapVerification
package-lock.json.npm audit: 0 vulnerabilities.format:check, lint (0 errors — the onereact-hooks/set-state-in-effectwarning pre-exists on main), 87/87 tests, andnext buildall green locally.Supersedes
Dependabot will auto-close the individual bump PRs once this lands: #145, #147, #148, #149, #150, #152, #153, #154, and the
@hono/node-serverhalf of #155. #155'smcp-handlerv1→v2 is a breaking, non-security major and deliberately stays out (still needs theroute.tsmigration or a@dependabot ignore). #151 was already stale.