Google Git
Sign in
chromium / chromium / src / 97d8060a92153def365904f1d0c9576007adef65
commit97d8060a92153def365904f1d0c9576007adef65[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Sat Dec 13 00:12:57 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Dec 13 00:12:57 2025
treec1ea7505c14aa94699fe3ea012b090d9bcb72be0
parent8e74ae3462a21bee6b1520126e53dca69df7878d [diff]
Roll Enterprise Companion chromium_win_x86_64 from TeNipVx8r7a00gwBP... to nAStYiaSlXJA4HyBq...

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-win-x86-64-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Enterprise Companion chromium_win_x86_64: https://g-issues.chromium.org/issues/new?component=1604672&template=0

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-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: I8e436ca2957e9d69fa983030b9dde3f6e43034e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7256804
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1558344}
1 file changed
tree: c1ea7505c14aa94699fe3ea012b090d9bcb72be0
  1. .gemini/
  2. .github/
  3. agents/
  4. android_webview/
  5. apps/
  6. ash/
  7. base/
  8. build/
  9. build_overrides/
  10. buildtools/
  11. cc/
  12. chrome/
  13. chromecast/
  14. chromeos/
  15. codelabs/
  16. components/
  17. content/
  18. crypto/
  19. dbus/
  20. device/
  21. docs/
  22. extensions/
  23. fuchsia_web/
  24. gin/
  25. google_apis/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. net/
  34. pdf/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. clank
  51. clusterfuzz-data
  52. internal
  53. ios_internal
  54. signing_keys
  55. v8
  56. .clang-format
  57. .clang-tidy
  58. .clangd
  59. .cursorignore
  60. .geminiignore
  61. .git-blame-ignore-revs
  62. .gitallowed
  63. .gitattributes
  64. .gitignore
  65. .gitmodules
  66. .gn
  67. .mailmap
  68. .rustfmt.toml
  69. .vpython3
  70. .yapfignore
  71. ATL_OWNERS
  72. AUTHORS
  73. BUILD.gn
  74. CODE_OF_CONDUCT.md
  75. codereview.settings
  76. CPPLINT.cfg
  77. CRYPTO_OWNERS
  78. DEPS
  79. DIR_METADATA
  80. LICENSE
  81. LICENSE.chromium_os
  82. OWNERS
  83. PRESUBMIT.py
  84. PRESUBMIT_test.py
  85. PRESUBMIT_test_mocks.py
  86. README.md
  87. SECURITY_OWNERS
  88. WATCHLISTS
README.md

Logo Chromium

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.