chore(deps-dev): bump chrome-devtools-frontend from 1.0.1638082 to 1.0.1641723 in the bundled-devtools group#2184
Merged
Lightning00Blade merged 1 commit intoJun 8, 2026
Conversation
Bumps the bundled-devtools group with 1 update: [chrome-devtools-frontend](https://github.com/ChromeDevTools/devtools-frontend). Updates `chrome-devtools-frontend` from 1.0.1638082 to 1.0.1641723 - [Commits](ChromeDevTools/devtools-frontend@v1.0.1638082...v1.0.1641723) --- updated-dependencies: - dependency-name: chrome-devtools-frontend dependency-version: 1.0.1641723 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: bundled-devtools ... Signed-off-by: dependabot[bot] <support@github.com>
Lightning00Blade
approved these changes
Jun 8, 2026
|
Ok
Em seg., 8 de jun. de 2026 às 05:57, github-merge-queue[bot] <
***@***.***> escreveu:
… Merged #2184
<#2184> into
main.
—
Reply to this email directly, view it on GitHub
<#2184?email_source=notifications&email_token=CDNASINYGEVQLOZKOEO6V5T46Z5WDA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENRUGYYTKNRUHA4TPJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#event-26461564897>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CDNASIPAORX23JJR2NOIIWT46Z5WDAVCNFSM6AAAAACZ5Q7336VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRWGQ3DCNJWGQ4DSNY>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CDNASIKAXK5UQTIUUMX5OM346Z5WDA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENRUGYYTKNRUHA4TPJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG>
and Android
<https://github.com/notifications/mobile/android/CDNASIP447UGICKKNOUI63T46Z5WDA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENRUGYYTKNRUHA4TPJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>.
Download it today!
You are receiving this because you are subscribed to this thread.Message
ID: <ChromeDevTools/chrome-devtools-mcp/pull/2184/issue_event/26461564897@
github.com>
|
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.
Bumps the bundled-devtools group with 1 update: chrome-devtools-frontend.
Updates
chrome-devtools-frontendfrom 1.0.1638082 to 1.0.1641723Commits
cf513d1Update DevTools DEPS (trusted)3bd6532[Lighthouse] Propagate CDP errors as ProtocolErrors65ecd64[A11y] Keep toggled toolbar icons visible in forced-colors mode0230d84Expand OS text scale emulation rangea1e097dFix CXX extension and chai importsc9fc4c5[EVP] Show new EVP issues in devtoolsd219c65[Sheriff]: Disable failing CPUThrottlingSelector test.2a985b9Update deps of targets to match the included filesf746bbcAI: Sanitize GCA label values to conform to GCP regex constraints7fb629dRoll browser-protocol and CfTDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions