Skip to content

chore(deps): patch 13 Dependabot advisories via pnpm overrides - #1180

Merged
teallarson merged 2 commits into
mainfrom
teallarson/dependabot
Sep 8, 2026
Merged

chore(deps): patch 13 Dependabot advisories via pnpm overrides#1180
teallarson merged 2 commits into
mainfrom
teallarson/dependabot

Conversation

@teallarson

@teallarson teallarson commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Closes 13 of the 15 open Dependabot alerts on this repo.

Changes

Package Was Now Alerts
postcss (direct + transitive) 8.5.19 8.5.26 #247, #246, #242
mermaid 11.15.0 11.17.2 #252, #251, #250, #249, #248
nanoid 3.3.12 3.3.18 #257, #256
dompurify 3.4.12 3.4.14 #253
fflate 0.4.8 0.4.9 #261
@xmldom/xmldom 0.9.10 0.9.12 #260

All six are pinned through pnpm-workspace.yaml overrides (matching the existing pattern in that file), with caps that stay inside each consumer's declared range. postcss is also bumped as a direct dependency in package.json.

Not fixed: qs (#259, #258)

The only patched release is qs@6.16.0, published 2026-08-29. This repo sets minimumReleaseAge: 10080 (7 days) to guard against supply-chain attacks, and 6.16.0 does not clear that window until 2026-09-05. Adding the override now would mean pulling a package the repo's own policy says to wait on, so it's left for a follow-up tomorrow.

postcss is capped at <8.5.27 for the same reason — 8.5.27 and 8.5.28 both shipped 2026-09-03. 8.5.26 is well past the 8.5.23 fix.

Verification

  • pnpm install clean
  • pnpm build succeeds
  • pnpm test — 875 tests across 69 files pass

🤖 Generated with Claude Code


Note

Low Risk
Changes are dependency and lockfile-only security patches with version caps inside consumer semver ranges; no auth or business logic is modified.

Overview
Addresses 13 open Dependabot alerts by tightening pnpm-workspace.yaml overrides and refreshing the lockfile, with no application source changes.

Direct bump: postcss in package.json goes from 8.5.15 → 8.5.26, with the override pinned to that version (not a range) so it aligns with Next’s transitive PostCSS while staying outside the repo’s 7-day minimumReleaseAge window for newer 8.5.27+ releases.

New or raised override floors force patched transitive versions: mermaid (11.17.2), nanoid, fflate, stricter dompurify and @xmldom/xmldom, plus the existing postcss alignment. Comments in the workspace file document which CVEs/GHSAs each floor targets.

The lockfile reflects the cascade (e.g. Mermaid parser/cytoscape/katex bumps, removal of deprecated @xmldom/xmldom@0.9.10). qs advisories are intentionally left for a follow-up once a patched release clears minimumReleaseAge.

Reviewed by Cursor Bugbot for commit ea8f06e. Bugbot is set up for automated code reviews on this repo. Configure here.

Bumps postcss to 8.5.26 and adds/raises overrides for mermaid, nanoid,
fflate, dompurify, and @xmldom/xmldom.

qs is left alone: the only patched release (6.16.0) was published
2026-08-29 and is still inside the repo's 7-day minimumReleaseAge
window. It ages out 2026-09-05.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs Ready Ready Preview Sep 8, 2026 2:57pm UTC

Request Review

@teallarson
teallarson marked this pull request as ready for review September 4, 2026 19:03
@teallarson
teallarson requested a review from sdreyer September 4, 2026 19:09
@teallarson teallarson assigned kamath and unassigned kamath Sep 4, 2026
@teallarson
teallarson requested a review from kamath September 4, 2026 19:09
@teallarson
teallarson enabled auto-merge (squash) September 8, 2026 13:56
Comment thread pnpm-workspace.yaml Outdated
postcss: ">=8.5.15"
# rule-engine pulls a vulnerable @xmldom/xmldom (XML injection / uncontrolled recursion)
"@xmldom/xmldom": ">=0.9.10"
# Force next's transitive postcss to the same safe version as the direct dep. 8.5.23 fixes the sourceMappingURL arbitrary .map file read (GHSA-6g55-p6wh-862q follow-up). Capped below 8.5.27 because later releases are still inside the 7-day minimumReleaseAge window above; raise the cap once they age out.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Idk if this is good practice? Pinning a highest version feels wrong, what happens if we just wait three days to avoid the 7-day window? Or we can come back in three days to remove the cap

@teallarson teallarson Sep 8, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I pinned to an exact version.

But also open to just waiting two more days.

Replace the patch-level semver cap with an exact pin matching package.json,
consistent with other overrides like esbuild and form-data.

Co-authored-by: Cursor <cursoragent@cursor.com>
@teallarson
teallarson merged commit 325c047 into main Sep 8, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants