commit | c9e47df396a1bd4f761f0256d19a200c950a1bc9 | [log] [tgz] |
---|---|---|
author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Tue Apr 08 18:39:26 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 08 18:39:26 2025 |
tree | 5430a97ef129194f08ccab2467465b883fc5ae51 | |
parent | ed7d1276210921e2804acc85e65d06f8d882cf7e [diff] |
Roll Release Scripts from ff9efcd1ae24 to 75179832e945 (1 revision) https://chrome-internal.googlesource.com/chrome/tools/release/scripts.git/+log/ff9efcd1ae24..75179832e945 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,gbeaty@google.com,hypan@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: gbeaty@google.com,hypan@google.com Change-Id: I648c68bd9072315be4002e54e4ba36a045b645b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6441436 Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1444270}
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.