Skip to content

Conversation

@browser-automation-bot
Copy link
Collaborator

🤖 I have created a release beep boop

0.2.7 (2025-09-24)

Bug Fixes

  • validate and report incompatible Node versions (#113) (adfcecf)

This PR was generated with Release Please. See documentation.

@OrKoN OrKoN merged commit 3181d70 into main Sep 24, 2025
16 checks passed
@OrKoN OrKoN deleted the release-please--branches--main--components--chrome-devtools-mcp branch September 24, 2025 12:55
@browser-automation-bot
Copy link
Collaborator Author

🤖 Created releases:

🌻

OzTamir pushed a commit to OzTamir/chrome-devtools-mcp that referenced this pull request Sep 25, 2025
🤖 I have created a release *beep* *boop*
---


##
[0.2.7](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v0.2.6...chrome-devtools-mcp-v0.2.7)
(2025-09-24)


### Bug Fixes

* validate and report incompatible Node versions
([ChromeDevTools#113](ChromeDevTools#113))
([adfcecf](ChromeDevTools@adfcecf))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
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