Skip to content

chore(main): release chrome-devtools-mcp 0.22.0#1876

Open
browser-automation-bot wants to merge 1 commit intomainfrom
release-please--branches--main--components--chrome-devtools-mcp
Open

chore(main): release chrome-devtools-mcp 0.22.0#1876
browser-automation-bot wants to merge 1 commit intomainfrom
release-please--branches--main--components--chrome-devtools-mcp

Conversation

@browser-automation-bot
Copy link
Copy Markdown
Collaborator

🤖 I have created a release beep boop

0.22.0 (2026-04-16)

🎉 Features

  • add tool call params logging (#1863) (528309a)
  • add update notification to both binaries (#1783) (e01e333)
  • ensure extensions for file outputs (#1867) (e7a0d50)
  • experimental click_at(x,y) tool (#1788) (c4f5471)
  • 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

  • remove double space in navigate error message (#1847) (429e0ca)

📄 Documentation

  • 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)

This PR was generated with Release Please. See documentation.

@OrKoN OrKoN force-pushed the release-please--branches--main--components--chrome-devtools-mcp branch from 47d2bd5 to a72f849 Compare April 16, 2026 13:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant