chore(deps): bump mermaid from 11.15.0 to 11.16.1 - #3484
Conversation
Bumps [mermaid](https://github.com/mermaid-js/mermaid) from 11.15.0 to 11.16.1. - [Release notes](https://github.com/mermaid-js/mermaid/releases) - [Commits](https://github.com/mermaid-js/mermaid/compare/mermaid@11.15.0...mermaid@11.16.1) --- updated-dependencies: - dependency-name: mermaid dependency-version: 11.16.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 0bf619c. Configure here.
| "marked": "^16.3.0", | ||
| "mdast-util-mdx-jsx": "^3.2.0", | ||
| "mermaid": "^11.15.0", | ||
| "mermaid": "^11.16.1", |
There was a problem hiding this comment.
Subgraph direction edges may break
Medium Severity
Bumping mermaid to 11.16.1 pulls in the 11.16.0 Dagre change that breaks edges into subgraphs that declare an inner direction. The incident-report flowchart uses that pattern (direction TB inside region subgraphs, with edges from Cloudflare into those ALBs), so those cross-subgraph links can fail to render. The 11.16.1 notes cover security and other patches, not that flowchart regression.
Reviewed by Cursor Bugbot for commit 0bf619c. Configure here.
There was a problem hiding this comment.
LGTM — straightforward dependency bump.
What was reviewed: confirmed the diff is limited to package.json/pnpm-lock.yaml with no application source changes; checked that the mermaid component still uses the same dynamic import("mermaid") API surface unaffected by this bump; verified the lockfile's transitive updates (dompurify, cytoscape, AWS SDK) are consistent version bumps, not manual edits.
Extended reasoning...
Overview
This PR is a Dependabot-generated dependency bump of mermaid from 11.15.0 to 11.16.1 (a patch/minor semver-compatible upgrade). Only package.json (one version string) and pnpm-lock.yaml (regenerated lockfile) are touched. No application code, components, or docs content are modified.
Security risks
None introduced by this PR. The mermaid 11.16.1 release notes actually include a security fix (increased protections against prototype pollution, GHSA-c4c3-pg64-4m4v), making this bump a net positive from a security standpoint. The lockfile also picks up a dompurify bump (3.3.3 -> 3.4.13 as a new resolved version alongside the existing one) which is a legitimate transitive dependency of the newer mermaid/iconify chain, not a manual or suspicious edit.
Level of scrutiny
Low scrutiny is appropriate here: this is a lockfile-only, semver-compatible dependency bump for a client-side diagramming library with no first-party code changes. The change is mechanical and fully generated by Dependabot tooling.
Other factors
A bug-hunting pass already ran and found no issues, and additionally investigated whether the mermaid bump causes duplicate dompurify copies via lockfile dedup — ruled out as not a real problem (multiple resolved versions in a pnpm lockfile is normal and expected, not a bug). No outstanding review comments exist on this PR, and there's no prior review from me to reconcile against.


Bumps mermaid from 11.15.0 to 11.16.1.
Release notes
Sourced from mermaid's releases.
... (truncated)
Commits
7ecca0cVersion Packages (#8023)95b1b9cdocs: changemermaidAPI.setConfig()changeset (#8024)acc69f1Merge pull request #8022 from mermaid-js/release/11.16.1eba7287docs: point changesets to correct commit hashes12d472cMerge commit from fork2cd6dcfMerge commit from fork630aa7eMerge commit from fork59b22faMerge commit from fork99af3fcMerge commit from fork2337f7eMerge branch 'test/improve-example.html' into release/11.16.1Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Note
Low Risk
Lockfile-only semver patch/minor bump for a client-side diagram library; main residual risk is rare rendering or parsing regressions in existing Mermaid blocks, offset by included security fixes.
Overview
Dependency-only update:
mermaidis raised from^11.15.0to^11.16.1inpackage.json, with the correspondingpnpm-lock.yamlrefresh (including transitive updates such as@mermaid-js/parser, cytoscape, dompurify, and optional AWS SDK entries tied to the lockfile graph).There are no application source changes—diagrams still load through the existing client
Mermaidcomponent and dynamicimport("mermaid").The upgrade pulls in 11.16.1 security and bug fixes (notably stronger prototype-pollution protections for user-controlled diagram input, plus CSS/architecture/xychart/radar fixes) and 11.16.0 diagram features that docs can use without code changes (new beta diagram types, treeView/architecture/gantt/ER/pie enhancements).
Reviewed by Cursor Bugbot for commit 0bf619c. Bugbot is set up for automated code reviews on this repo. Configure here.