chore(deps): update dependency chrome-devtools-mcp to v0.22.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
chrome-devtools-mcp	0.20.0 → 0.22.0

---

Release Notes

ChromeDevTools/chrome-devtools-mcp (chrome-devtools-mcp)

v0.22.0

Compare Source

🎉 Features

• add update notification to both binaries (#​1783) (e01e333)
• auto handle dialogs during script evaluation (#​1839) (da33cb5)
• ensure extensions for file outputs (#​1867) (e7a0d50)
• experimental click_at(x,y) tool (#​1788) (c4f5471)
• support Chrome extensions debugging (#​1922) (3ff21cf)
• support DevTools header redactions as an option (#​1848) (5c398c4)
• webmcp: Add experimental tool to execute WebMCP tool (#​1873) (0aff266)
• webmcp: Add experimental tool to list WebMCP tools page exposes (#​1845) (f97b573)

🛠️ Fixes

• avoid showing update notification for local builds (#​1889) (3f0cf10), closes #​1886
• cli: correct WebP MIME type check in handleResponse ('webp' → 'image/webp') (#​1899) (e3a5f6b), closes #​1898
• ignore unmapped PerformanceIssue events (#​1852) (ea57e86)
• network: trailing data in Network redirect chain (#​1880) (2f458c1)
• remove double space in navigate error message (#​1847) (429e0ca)

📄 Documentation

• clarify tools included into CLI (#​1925) (76ab9fa)
• document network response and request extensions (#​1887) (796d6f2)
• fix skill and reference documentation issues (#​1249) (9236834)
• Include Mistral Vibe setup in README (#​1801) (582c9e0)
• Rename project and enhance README content (#​1856) (c066488)
• update the README on installing as a VS code agent plugin (#​1796) (1b5dcae)

🏗️ Refactor

• move waitForEventsAfterAction to McpPage (#​1780) (c7c8f50)
• use puppeteer Extension API (#​1911) (ec895f1)

v0.21.0

Compare Source

🎉 Features

• add a skill for detecting memory leaks using take_memory_snapshot tool (#​1162) (d19a235)

🛠️ Fixes

• cli: avoid defaulting to isolated when userDataDir is provided (#​1258) (73e1e24)
• list_pages should work after selected page is closed (#​1145) (2664455)
• mark lighthouse and memory as non-read-only (#​1769) (bec9dae)
• telemetry: record client name (9a47b65)
• versioning for Claude Code plugin (#​1233) (966b86f)
• wrap .mcp.json config in mcpServers key (#​1246) (c7948cf)

📄 Documentation

• Command Code CLI instructions for MCP server (0a7c0a7)
• provide disclaimer about supported browsers (#​1237) (8676b72)

🏗️ Refactor

• set process titles for easier debugging (#​1770) (0fe3896)

v0.20.3

Compare Source

🛠️ Fixes

• mark categoryExtensions flag mutually exclusive with autoConnect (#​1202) (8c2a7fc), closes #​1072

⚡ Performance

• memory: release old navigation request in NetworkCollector (#​1200) (1e6456c)
• use CDP to find open DevTools pages (reland) (#​1210) (53483bc)

v0.20.2

Compare Source

📄 Documentation

• add troubleshooting for Claude Code plugin HTTPS clone failures (#​1195) (d082ca4)

v0.20.1

Compare Source

🛠️ Fixes

• update VS Code manual installation powershell command (#​1151) (6c64a5b)

⚡ Performance

• use CDP to find open DevTools pages. (#​1150) (94de19c)

---

Configuration

📅 Schedule: (UTC)

• 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 becomes conflicted, 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.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-actions]

🔒 MCP Security Scan Results

✅ chrome-devtools-mcp

• Status: Passed
• Tools scanned: 0
• Result: No security issues detected

---

Summary: Scanned 1 MCP server(s), all passed security checks. ✅

[rdimitrov]

@renovatebot rebase