commit | b8805dd069b9aef39f408a623d30394bea36a663 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Apr 03 21:23:45 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 03 21:23:45 2025 |
tree | b211adab3f57633dffa2a1ca4c216e21a810a818 | |
parent | fcc81b4b0132ad8a13d71339ccb66df98ee02230 [diff] |
Roll DevTools Frontend from 3606a94b4f1a to 30e9402e5fc3 (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/3606a94b4f1a..30e9402e5fc3 2025-04-03 liviurau@chromium.org Use correct realm for local rdb use If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@rotations.google.com,liviurau@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Bug: None Change-Id: I5395e65347573680be73edb645568de6d64c2ab8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6430943 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1442425}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.