Skip to content

Conversation

@sebastianbenz
Copy link
Collaborator

Setting the default channel in the CLI resulted in our mutually exclusive check for browserUrl and channel to fail.

@sebastianbenz sebastianbenz requested a review from OrKoN September 19, 2025 09:09
@OrKoN OrKoN changed the title Fix browserUrl not working fix: fix browserUrl not working Sep 19, 2025
Copy link
Collaborator

@OrKoN OrKoN left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some checks are failing. PTAL

@sebastianbenz sebastianbenz force-pushed the fix-cli branch 2 times, most recently from c8a76f8 to 4cd7103 Compare September 19, 2025 10:00
Setting the default channel in the CLI resulted in our mutually exclusive check
for browserUrl and channel to fail.
@sebastianbenz sebastianbenz merged commit a6923b8 into main Sep 19, 2025
15 of 17 checks passed
@sebastianbenz sebastianbenz deleted the fix-cli branch September 19, 2025 10:24
OrKoN pushed a commit that referenced this pull request Sep 23, 2025
🤖 I have created a release *beep* *boop*
---


##
[0.2.1](chrome-devtools-mcp-v0.2.0...chrome-devtools-mcp-v0.2.1)
(2025-09-23)


### Bug Fixes

* add 'on the selected page' to performance tools
([#69](#69))
([b877f7a](b877f7a))
* **emulation:** correctly report info for selected page
([#63](#63))
([1e8662f](1e8662f))
* expose timeout when Emulation is enabled
([#73](#73))
([0208bfd](0208bfd))
* fix browserUrl not working
([#53](#53))
([a6923b8](a6923b8))
* increase timeouts in case of Emulation
([#71](#71))
([c509c64](c509c64))
* **windows:** work around Chrome not reporting reasons for crash
([#64](#64))
([d545741](d545741))

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