fix(telemetry): re-run the update metrics script#2005
Merged
Conversation
wolfib
approved these changes
May 7, 2026
Contributor
wolfib
left a comment
wolfib
left a comment
There was a problem hiding this comment.
Thanks for the fix and the explanation!
I did indeed manually edit the files in my PR.
masamaru0513
pushed a commit
to masamaru0513/chrome-devtools-mcp
that referenced
this pull request
May 12, 2026
🤖 I have created a release *beep* *boop* --- ## [0.26.0](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v0.25.0...chrome-devtools-mcp-v0.26.0) (2026-05-11) ### 🎉 Features * add an error logging method ([ChromeDevTools#2006](ChromeDevTools#2006)) ([06e0ab6](ChromeDevTools@06e0ab6)) ### 🛠️ Fixes * **cli:** allow --autoConnect on CLI start ([ChromeDevTools#2015](ChromeDevTools#2015)) ([9882391](ChromeDevTools@9882391)), closes [ChromeDevTools#1859](ChromeDevTools#1859) [ChromeDevTools#1184](ChromeDevTools#1184) * Make fill_form more appealing when filling forms with checkboxes ([ChromeDevTools#1971](ChromeDevTools#1971)) ([407c2bd](ChromeDevTools@407c2bd)) * only require a page in page-scoped tools ([ChromeDevTools#2030](ChromeDevTools#2030)) ([8e06761](ChromeDevTools@8e06761)) * **telemetry:** re-run the update metrics script ([ChromeDevTools#2005](ChromeDevTools#2005)) ([e9ec375](ChromeDevTools@e9ec375)) ### 📄 Documentation * Fix Claude Code instructions ([ChromeDevTools#2018](ChromeDevTools#2018)) ([a5ad67b](ChromeDevTools@a5ad67b)) ### 🏗️ Refactor * extract ToolHandler ([ChromeDevTools#2032](ChromeDevTools#2032)) ([178b790](ChromeDevTools@178b790)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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.
the updates made to these files from #1982 came out a bit weird. So I reverted changes on these files and re-run
npm run gen(which includesnpm run update-metrics) to correct them.we'd always want old entries to be marked as deprecated and new entries to be added to the very last. Don't manually resolve conflicts in these files. When there are conflicts, just revert back to a clean state and
npm run genwill take care of them 😉