chore(main): release chrome-devtools-mcp 0.12.1 #663
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
browser-automation-bot
force-pushed
the
release-please--branches--main--components--chrome-devtools-mcp
branch
4 times, most recently
from
f12e1b1 to
909fec7
Compare
browser-automation-bot
force-pushed
the
release-please--branches--main--components--chrome-devtools-mcp
branch
from
909fec7 to
5be497d
Compare
OrKoN
approved these changes
Dec 12, 2025
OrKoN
deleted the
release-please--branches--main--components--chrome-devtools-mcp
branch
Collaborator
Author
|
🤖 Created releases: 🌻 |
browser-automation-bot
added
autorelease: tagged
and removed
autorelease: pending
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.12.1 (2025-12-12)
🛠️ Fixes
📄 Documentation
This PR was generated with Release Please. See documentation.