| commit | a88b02e54c8157df975b3769a80ce028a129b55c | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Jul 08 02:50:28 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 08 02:50:28 2025 |
| tree | 7f3a2ab50505b12ad499276715040b9a37b46304 | |
| parent | e63262a0716e7bbaa2b553fcbfb9faa7b3635c21 [diff] |
Roll Depot Tools from abc510988246 to 1b7c452940c0 (1 revision) https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/abc510988246..1b7c452940c0 2025-07-08 rop@google.com Add Vuln scan sufficiency to metadata. 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 chops-source-team@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: None Tbr: Change-Id: I63d3412e3e9ef0228d00f604853265092911015e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6711390 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@{#1483505}
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.