Conversation
This reverts commit a10f591.
wolfib
changed the title
wolfib
changed the title
OrKoN
approved these changes
Mar 31, 2026
OrKoN
pushed a commit
to mvanhorn/chrome-devtools-mcp
that referenced
this pull request
Apr 1, 2026
Reverts ChromeDevTools#1764 The goal is to trigger another run of release-please. The [previous run](ChromeDevTools#1215) did not pick up updated PR titles, so now I have updated PR descriptions [(1)](https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1239)[(2)](https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1762) in the hope that this causes the appropriate update in the release PR.
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
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.
Reverts #1764
The goal is to trigger another run of release-please. The previous run did not pick up updated PR titles, so now I have updated PR descriptions (1)(2) in the hope that this causes the appropriate update in the release PR.