commit | 1a00d4b30752a5f05a2008f82ecfc5005336448f | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Jun 24 22:52:57 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 24 22:52:57 2025 |
tree | bd24090919598ddd5633f999060a66ae43f6179b | |
parent | b877cc4495508e427424d7a13dd5c4b64f450c6c [diff] |
Roll Depot Tools from 488ad9dd221f to 4c626451ae01 (1 revision) https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/488ad9dd221f..4c626451ae01 2025-06-24 rgw@google.com [lucicfg] Update lucicfg 1.45.4 to 1.45.5 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC begizi@google.com,chops-source-team@google.com,ddoman@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry 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 Cq-Include-Trybots: luci.chromium.try:linux-utr-tester;luci.chromium.try:win-utr-tester Bug: chromium:407539622 Tbr: begizi@google.com,ddoman@google.com Change-Id: I3a5ec57232b904ac2453dba5e014878161772b38 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6669829 Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1478234}
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.