Skip to content

docs: remove outdated --channel=beta note#882

Merged
OrKoN merged 1 commit intoChromeDevTools:mainfrom
vibecodingengine:fix/remove-outdated-beta-channel-note
Feb 4, 2026
Merged

docs: remove outdated --channel=beta note#882
OrKoN merged 1 commit intoChromeDevTools:mainfrom
vibecodingengine:fix/remove-outdated-beta-channel-note

Conversation

@vibecodingengine
Copy link
Contributor

Summary

Chrome M144 is now in the stable channel, so the note about requiring --channel=beta and the example configuration using it are outdated.

Prompt

Remove outdated documentation about --channel=beta since Chrome M144 is now in stable channel.

Changes

  • Removed --channel=beta from the --autoConnect example configuration
  • Removed the note: "Note: you have to specify --channel=beta until Chrome M144 has reached the stable channel."

Test plan

  • Verified the documentation now reflects the current stable Chrome version

🤖 Generated with Claude Code

@google-cla
Copy link

google-cla bot commented Feb 4, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@vibecodingengine vibecodingengine force-pushed the fix/remove-outdated-beta-channel-note branch from c634849 to 4b48e46 Compare February 4, 2026 04:51
Chrome M144 is now in the stable channel, so the note about requiring
--channel=beta and the example configuration using it are outdated.

Changes:
- Removed --channel=beta from autoConnect example configuration
- Removed note stating --channel=beta is required until M144 reaches stable
@vibecodingengine vibecodingengine force-pushed the fix/remove-outdated-beta-channel-note branch from 4b48e46 to f55b38c Compare February 4, 2026 09:27
@OrKoN OrKoN enabled auto-merge February 4, 2026 09:29
@OrKoN
Copy link
Collaborator

OrKoN commented Feb 4, 2026

Thanks!

@OrKoN OrKoN added this pull request to the merge queue Feb 4, 2026
Merged via the queue into ChromeDevTools:main with commit acdb5c9 Feb 4, 2026
36 of 43 checks passed
github-merge-queue bot pushed a commit that referenced this pull request Feb 4, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.16.0](chrome-devtools-mcp-v0.15.1...chrome-devtools-mcp-v0.16.0)
(2026-02-04)


### 🎉 Features

* include source-mapped stack trace for uncaught errors
([#876](#876))
([ecef712](ecef712))


### 🛠️ Fixes

* accidental extra typing in the fill tool
([#886](#886))
([3d6e59d](3d6e59d))
* update evaluateScript description formatting
([#880](#880))
([24db9dd](24db9dd))
* use 1-based line/column and fix wasm offsets in stack frames
([#884](#884))
([7e1ec81](7e1ec81))


### 📄 Documentation

* mention source-mapped stack traces in 'Key features'
([#883](#883))
([579d18a](579d18a))
* remove outdated --channel=beta note
([#882](#882))
([acdb5c9](acdb5c9))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
@vibecodingengine vibecodingengine deleted the fix/remove-outdated-beta-channel-note branch February 6, 2026 17:38
wolfib pushed a commit to wolfib/chrome-devtools-mcp that referenced this pull request Mar 10, 2026
## Summary
Chrome M144 is now in the stable channel, so the note about requiring
`--channel=beta` and the example configuration using it are outdated.

## Prompt
Remove outdated documentation about --channel=beta since Chrome M144 is
now in stable channel.

## Changes
- Removed `--channel=beta` from the `--autoConnect` example
configuration
- Removed the note: "Note: you have to specify `--channel=beta` until
Chrome M144 has reached the stable channel."

## Test plan
- [x] Verified the documentation now reflects the current stable Chrome
version

🤖 Generated with [Claude Code](https://claude.com/claude-code)
wolfib pushed a commit to wolfib/chrome-devtools-mcp that referenced this pull request Mar 10, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.16.0](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v0.15.1...chrome-devtools-mcp-v0.16.0)
(2026-02-04)


### 🎉 Features

* include source-mapped stack trace for uncaught errors
([ChromeDevTools#876](ChromeDevTools#876))
([ecef712](ChromeDevTools@ecef712))


### 🛠️ Fixes

* accidental extra typing in the fill tool
([ChromeDevTools#886](ChromeDevTools#886))
([3d6e59d](ChromeDevTools@3d6e59d))
* update evaluateScript description formatting
([ChromeDevTools#880](ChromeDevTools#880))
([24db9dd](ChromeDevTools@24db9dd))
* use 1-based line/column and fix wasm offsets in stack frames
([ChromeDevTools#884](ChromeDevTools#884))
([7e1ec81](ChromeDevTools@7e1ec81))


### 📄 Documentation

* mention source-mapped stack traces in 'Key features'
([ChromeDevTools#883](ChromeDevTools#883))
([579d18a](ChromeDevTools@579d18a))
* remove outdated --channel=beta note
([ChromeDevTools#882](ChromeDevTools#882))
([acdb5c9](ChromeDevTools@acdb5c9))

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