Roll WebRTC from 33f3b4a35612 to 54aeeeb6f8ae (5 revisions) https://webrtc.googlesource.com/src.git/+log/33f3b4a35612..54aeeeb6f8ae 2025-08-22 eshr@webrtc.org Add environment accessor to call 2025-08-22 webrtc-version-updater@webrtc-ci.iam.gserviceaccount.com Update WebRTC code version (2025-08-22T04:08:15). 2025-08-21 phancke@meta.com clang-tidy: apply modernize-use-designated-initializer to examples/ net/ rtc_tools/ test 2025-08-21 phancke@meta.com sigslot: make PortInterface::SignalRoleConflict a CallbackLst 2025-08-21 sprang@webrtc.org Move FrameInstrumentationEvaluation to api/video/corruption_detection. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com,webrtc-infra@google.com on the revert to ensure that a human is aware of the problem. To file a bug in WebRTC: https://bugs.chromium.org/p/webrtc/issues/entry 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 Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Id062e6c0b97378f37879cde5ccf4e504692a6cbc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6874490 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@{#1504963}
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.