commit | 76d68caff2b856fb6a8e14045f6ac73bd45716fd | [log] [tgz] |
---|---|---|
author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Fri Apr 04 20:53:38 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 04 20:53:38 2025 |
tree | 2f685ded330931d98aba59e289aa6d6951f483eb | |
parent | 54b6acad441442c2d33c96acabe065e35dce62dd [diff] |
Roll Release Scripts from fa36d66dc366 to b10a3aa0f2f1 (1 revision) https://chrome-internal.googlesource.com/chrome/tools/release/scripts.git/+log/fa36d66dc366..b10a3aa0f2f1 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,jiesheng@google.com,morawand@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: jiesheng@google.com,morawand@google.com Change-Id: Ie35c030ea19768d01976c13bb2228d1e879ce535 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6434665 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@{#1442909}
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.