chore(deps): bump mermaid to 11.16.1 - #52
Conversation
Clears five Dependabot alerts against the docs site: prototype pollution through the configuration APIs and through architecture diagrams, CSS injection into sibling elements, and denial of service in radar and XY chart rendering. Refreshes the pnpmDeps hash, which the lockfile change invalidates.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 24 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Comment |
commit: |
Related Issue
No issue. The problem is described below.
Problem
Dependabot reports nine open alerts against
main. Five of them aremermaid@11.16.0, a direct dependency of the documentation site:All five are fixed in
11.16.1, which the declared^11.16.0range already permits — only the lockfile held the old version.What changed
mermaidmoves to11.16.1indocs/package.jsonand the lockfile.pnpmDepshash inflake.nixis refreshed, because any lockfile change invalidates it.The remaining four alerts are out of scope and cannot be fixed here. They are
vite@5.4.21(one high, two medium) and itsesbuild@0.21.5dependency, both reached only throughvitepress@1.6.4, which is the latest stable release and pinsvite: ^5.4.14. The fix exists only invite@6.4.3with no 5.x backport, so clearing them needs VitePress 2.0, currently an alpha. Every one of those advisories is a development-server issue, and the vulnerable copy exists only underdocs/— the other five workspaces already pinvite ^6.4.3.Verification
nix build .#pythinker-code.pnpmDepspasses with the new hash. The old hash was confirmed stale by forcing a mismatch: a fixed-output derivation is content-addressed, so a local build reuses the cached path and reports success even when the lockfile has moved.node scripts/check-nix-workspace.mjspasses.pnpm exec vitest runpasses: 651 files, 9949 tests.Checklist
gen-changesetsskill, or this PR needs no changeset. — No changeset: the bump touches only the documentation site's dependencies and does not enter the CLI bundle.gen-docsskill, or this PR needs no doc update.