Skip to content

Conversation

@OrKoN
Copy link
Collaborator

@OrKoN OrKoN commented Sep 24, 2025

it appears that mcp registry publishing tools would not sync automatically with package.json.

@OrKoN OrKoN requested a review from sebastianbenz September 24, 2025 08:14
@OrKoN OrKoN enabled auto-merge (squash) September 24, 2025 08:15
@OrKoN OrKoN merged commit cae1cf1 into main Sep 24, 2025
10 checks passed
@OrKoN OrKoN deleted the orkon/bump-server-json-versions branch September 24, 2025 08:23
OrKoN pushed a commit that referenced this pull request Sep 24, 2025
🤖 I have created a release *beep* *boop*
---


##
[0.2.6](chrome-devtools-mcp-v0.2.5...chrome-devtools-mcp-v0.2.6)
(2025-09-24)


### Bug Fixes

* manually bump server.json versions based on package.json
([#105](#105))
([cae1cf1](cae1cf1))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
OzTamir pushed a commit to OzTamir/chrome-devtools-mcp that referenced this pull request Sep 25, 2025
…DevTools#105)

it appears that mcp registry publishing tools would not sync
automatically with package.json.
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.6](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v0.2.5...chrome-devtools-mcp-v0.2.6)
(2025-09-24)


### Bug Fixes

* manually bump server.json versions based on package.json
([ChromeDevTools#105](ChromeDevTools#105))
([cae1cf1](ChromeDevTools@cae1cf1))

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants