Skip to content

chore(main): release chrome-devtools-mcp 0.19.1#1126

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.19.1#1126
browser-automation-bot wants to merge 1 commit intomainfrom
release-please--branches--main--components--chrome-devtools-mcp

Conversation

@browser-automation-bot
Copy link
Collaborator

@browser-automation-bot browser-automation-bot commented Mar 5, 2026

🤖 I have created a release beep boop

0.19.1 (2026-03-09)

📄 Documentation

  • fix typos and improve phrasing (#1130) (70d4f36)
  • revise contribution process and add release process (#1134) (d7d26a1)
  • troubleshooting: add symptom for missing tools due to read-only mode (#1148) (57e7d51)
  • Update troubleshooting for MCP server connection errors (#1017) (00f9c31)

🏗️ Refactor


This PR was generated with Release Please. See documentation.

@browser-automation-bot browser-automation-bot force-pushed the release-please--branches--main--components--chrome-devtools-mcp branch 3 times, most recently from c35844e to 981e289 Compare March 6, 2026 12:16
@browser-automation-bot browser-automation-bot force-pushed the release-please--branches--main--components--chrome-devtools-mcp branch from 981e289 to 828a63f Compare March 9, 2026 08:50
@browser-automation-bot browser-automation-bot force-pushed the release-please--branches--main--components--chrome-devtools-mcp branch from 828a63f to a083513 Compare March 9, 2026 12:40
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.

2 participants