Skip to content

chore: update dependencies #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rubenhensen merged 3 commits into from
Jul 2, 2026
Merged

chore: update dependencies #116

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f246eb8
fix(deps): bump vite override to 6.4.3 and pin dompurify >=3.4.11
dobby-coder[bot] Jul 1, 2026
a4522fe
chore(deps): bump mermaid to 11.16.0
dobby-coder[bot] Jul 1, 2026
32d2db6
chore(deps): bump @e4a/pg-js to 2.1.0 (major)
dobby-coder[bot] Jul 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 24 additions & 24 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

7 changes: 4 additions & 3 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,15 +8,16 @@
"docs:preview": "vitepress preview docs"
},
"devDependencies": {
"@e4a/pg-js": "^1.10.0",
"@e4a/pg-js": "^2.1.0",
"vitepress": "^1.6.4"
},
"dependencies": {
"mermaid": "^11.15.0",
"mermaid": "^11.16.0",
"vitepress-plugin-mermaid": "^2.0.17"
},
"overrides": {
"esbuild": "^0.25.0",
"vite": "^6.4.2"
"vite": "^6.4.3",
"dompurify": ">=3.4.11"

@dobby-coder dobby-coder Bot Jul 1, 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.

The dompurify override is an unbounded lower-bound range (>=3.4.11). A future dompurify 4.x would satisfy it and be force-resolved into mermaid (which declares ^3.3.3), risking a silent breaking bump on a routine npm install. Prefer ^3.4.11 — it still resolves to the patched 3.4.11 and clears all 10 advisories, but caps the major so mermaid can't be pulled onto an incompatible dompurify. Non-blocking: currently resolves correctly and build/CI pass with 0 vulns, but it's a one-character hardening (>= → ^).

}
}
Loading