chore(deps): bump mermaid to 11.16.1 and js-yaml to 4.3.1 to clear open Dependabot alerts - #6375
Conversation
…en Dependabot alerts
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryLow Risk Overview
Because both releases are still inside the repo’s 7-day Reviewed by Cursor Bugbot for commit fddd10a. Configure here. |
Greptile SummaryThis PR upgrades the direct Mermaid and js-yaml dependencies to patched releases and updates the lockfile consistently. It also refreshes Bun’s minimum-release-age exceptions by adding temporary exceptions for the new releases and removing expired entries.
Confidence Score: 5/5The PR appears safe to merge with no actionable defects identified in the dependency or release-age configuration changes. The patched dependencies resolve coherently, existing application usage remains compatible, and the release-age exception updates do not create a reachable install, build, or runtime failure.
|
| Filename | Overview |
|---|---|
| apps/sim/package.json | Updates the application’s direct Mermaid and js-yaml pins; repository callers remain compatible with the patched releases. |
| bun.lock | Regenerates direct and transitive resolutions coherently, including Mermaid’s parser update and js-yaml’s direct patched resolution. |
| bunfig.toml | Removes expired release-age exclusions and temporarily exempts the newly pinned security releases. |
| package.json | Keeps the root Mermaid override aligned with the application dependency and lockfile. |
Reviews (1): Last reviewed commit: "chore(deps): bump mermaid to 11.16.1 and..." | Re-trigger Greptile
Summary
mermaid11.15.0 → 11.16.1, clearing five open Dependabot alerts: architecture-diagram and config-API prototype pollution, radar and XY-chart DoS, and CSS injection into siblings of the diagramjs-yaml4.3.0 → 4.3.1 for CVE-2026-59870 (quadratic CPU consumption in!!omapresolution), which was never backported to the 4.3.0 lineminimumReleaseAgesupply-chain gate, so each gets abunfig.tomlexception with a dated drop noteminimumReleaseAgeExcludesentries that have aged past the window (Pi 0.80.10 ×4,next/@next/env/@next/swc-*×6,@anthropic-ai/sdk,@e2b/code-interpreter,e2b) — verified they all still resolve to the same pinned versions with the exceptions removedNot covered here
Three transitive
js-yamlcopies remain on vulnerable versions:3.14.2(viagray-matter, needs 3.15.1) and4.2.0/4.3.0(via fumadocs, electron-builder,json-schema-to-typescript). Dependabot did not flag these — it only detected the direct manifest entry. A rootoverridesforcing 4.3.1 would breakgray-matter, which needs js-yaml 3'ssafeLoad, so these want a separate PR with per-package overrides.Type of Change
Testing
bun run type-checkclean. 55 mermaid/YAML tests pass acrosslib/mermaid,lib/file-parsers/yaml-parser,lib/chunkers/json-yaml-chunker, andfile-viewer/mermaid-diagram.Checklist