chore: resolve open Dependabot alerts

[sriramveeraghanta]

Resolves all 9 open Dependabot alerts on the repo (all transitive, all landing on pnpm-lock.yaml).

Package	Alerts	Before → After	Mechanism
dompurify	#79 (medium), #78 (low)	3.4.11 → 3.4.13	overrides: bump
postcss	#76 (medium), #71 (high)	8.5.15 → 8.5.23	overrides: bump
js-yaml	#73 (high)	3.15.0 → 3.15.1	overrides: bump
brace-expansion	#72, #70, #68 (high)	5.0.6 → 5.0.9	pnpm update -r
linkify-it	#69 (high)	5.0.1 → 5.0.2	pnpm update -r

Why two mechanisms

dompurify, postcss and js-yaml already have entries in the overrides: block of pnpm-workspace.yaml, which fixes their version tree-wide — Dependabot cannot compute an update past an override, so these only ever move by hand. Each new version still sits inside its consumers' declared ranges.

brace-expansion and linkify-it have no override entry, so they were bumped with pnpm update -r within their parents' declared ranges (minimatch 10.2.5, markdown-it 14.2.0) rather than pinned. Deliberately not adding overrides for these: an override applies tree-wide, and brace-expansion 5.x replaced the v1/v2 default export with a named expand, so pinning it would break any consumer still on minimatch 9.x.

Verification

• pnpm audit → no known vulnerabilities found
• pnpm dedupe --check → clean
• pnpm check:types → 3/3 tasks pass
• pnpm build → both sites build
• pnpm check:format → clean
• Each of the five packages resolves to exactly one version in the lockfile

https://claude.ai/code/session_0127W5LkKePrb8vVG9FFdFgG

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
developer-docs	Ready	Preview	Aug 21, 2026 8:09am
docs	Ready	Preview	Aug 21, 2026 8:09am

[coderabbitai]

Warning

Review limit reached

@sriramveeraghanta, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a9c45d76-a5b6-4f77-825c-40bbe8cb2641

📥 Commits

Reviewing files that changed from the base of the PR and between e0a1282 and 51aec34.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• pnpm-workspace.yaml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}