chore(deps): update dependency vitepress to v2.0.0-alpha.16

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vitepress (source)	2.0.0-alpha.15 → 2.0.0-alpha.16

---

Release Notes

vuejs/vitepress (vitepress)

v2.0.0-alpha.16

Compare Source

Bug Fixes

• always log error when failed to fetch page (66cf64e)
• theme: add fallback for heroImageSlotExists (#​5076) (f119b18)
• theme: align badges in h1 and h2 (#​5087) (closes #​5063) (b200865)
• theme: highlight active link in mobile nav menu (#​5086) (closes #​5068, closes #​5074) (923aa90)
• theme: overflow clip is buggy on safari (8ed6ea0), closes #​5050 #​5039 #​5027
• theme: remove margin between code groups and blocks in markdown containers (a28e171), closes #​5099

Features

• theme: upgrade DocSearch to 4.5 with sidepanel (#​5092) (0d646a6)
• theme: use @layer __vitepress_base to wrap the styles in base.css (#​4905) (f8d8c0d)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cloudflare-workers-and-pages]

Deploying egg-v3 with    Cloudflare Pages

Latest commit:	21cb291
Status:	✅  Deploy successful!
Preview URL:	https://9316cac1.egg-v3.pages.dev
Branch Preview URL:	https://renovate-vitepress-2-x.egg-v3.pages.dev

View logs

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

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

[cloudflare-workers-and-pages]

Deploying egg with    Cloudflare Pages

Latest commit:	21cb291
Status:	✅  Deploy successful!
Preview URL:	https://4e8db888.egg-cci.pages.dev
Branch Preview URL:	https://renovate-vitepress-2-x.egg-cci.pages.dev

View logs

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.57%. Comparing base (8c09d7b) to head (21cb291).

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #5784   +/-   ##
=======================================
  Coverage   87.57%   87.57%           
=======================================
  Files         563      563           
  Lines       10940    10940           
  Branches     1242     1242           
=======================================
  Hits         9581     9581           
  Misses       1275     1275           
  Partials       84       84           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	keygrip@​1.1.0
	@​types/​encodeurl@​1.0.3
	@​types/​koa-range@​0.3.5
	@​types/​lodash.snakecase@​4.1.9
	@​types/​sqlstring@​2.3.2
	@​types/​destroy@​1.0.3
	husky@​9.1.7
	@​types/​fresh@​0.5.3
	@​types/​fs-readdir-recursive@​1.1.3
	@​types/​vary@​1.1.3
	@​types/​parseurl@​1.3.3
	@​types/​on-finished@​2.3.5
	@​types/​stack-trace@​0.0.33
	@​types/​mime-types@​3.0.1
	@​types/​type-is@​1.6.7
	@​vitest/​coverage-v8@​4.0.15
	@​types/​js-beautify@​1.14.3
	@​types/​body-parser@​1.19.6
	@​types/​express@​5.0.3
	@​types/​js-yaml@​4.0.9
	@​typescript/​native-preview@​7.0.0-dev.20260117.1
	@​types/​nunjucks@​3.2.6
	@​types/​escape-html@​1.0.4
	@​types/​content-type@​1.1.9
	@​types/​common-tags@​1.8.4
	egg-plugin-puml@​2.4.0
	@​eggjs/​compressible@​3.0.0
	@​types/​extend@​3.0.4
	assert-file@​1.0.0
	esbuild@​0.27.0
	@​types/​safe-timers@​1.1.2
	@​types/​urijs@​1.19.25
	@​types/​mustache@​4.2.6
See 78 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm ioredis is 96.0% likely obfuscated Confidence: 0.96 Location: Package overview From: plugins/redis/package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm js-beautify is 100.0% likely obfuscated Confidence: 1.00 Location: Package overview From: pnpm-lock.yaml → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm markdown-it is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report