commit | c054621a204b70da41c5cfb5454c3412bc3cdb39 | [log] [tgz] |
---|---|---|
author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Thu Apr 10 04:02:23 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 10 04:02:23 2025 |
tree | 1e1f42b81a46da7e70660344064de3d2d08e8dc0 | |
parent | 394937587b05a0d1eb7d67bf7db25e6d1d03b182 [diff] |
Roll Release Scripts from 0d4a9ec0b2ed to 5ac510941a83 (1 revision) https://chrome-internal.googlesource.com/chrome/tools/release/scripts.git/+log/0d4a9ec0b2ed..5ac510941a83 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/release-scripts-chromium Please CC chrome-release-infra@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 Tbr: Change-Id: Ifb2450f8c6dcb5c2044e2d7449716bf9c95b0ffa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6444833 Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1445094}
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.