Kamil Jozwiak
859712f35c
Update from Chromium 140.0.7339.80 to Chromium 140.0.7339.133. (#31122)
<!-- Add brave-browser issue below that this PR will resolve -->
Resolves https://github.com/brave/brave-browser/issues/49123
<!-- CI-related labels that can be applied to this PR:
* CI/run-audit-deps (1) - check for known npm/cargo vulnerabilities
(audit_deps)
* CI/run-network-audit (1) - run network-audit
* CI/run-upstream-tests - run Chromium unit and browser tests on Linux
and Windows (otherwise only on Linux)
* CI/run-linux-arm64, CI/run-macos-x64, CI/run-windows-arm64,
CI/run-windows-x86 - run builds that would otherwise be skipped
* CI/skip - do not run CI builds (except noplatform)
* CI/skip-linux-x64, CI/skip-android, CI/skip-macos-arm64, CI/skip-ios,
CI/skip-windows-x64 - skip CI builds for specific platforms
* CI/skip-upstream-tests - do not run Chromium unit, or browser tests
(otherwise only on Linux)
* CI/skip-all-linters - do not run presubmit and lint checks
* CI/storybook-url (1) - deploy storybook and provide a unique URL for
each build
(1) applied automatically when some files are changed (see:
https://github.com/brave/brave-core/blob/master/.github/labeler.yml)
-->
<!--
## Checklist:
- Review design docs
[Browser design
principles](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/chrome_browser_design_principles.md)
[Style
guide](https://chromium.googlesource.com/chromium/src/+/main/styleguide/c++/c++.md)
[Core principles](https://www.chromium.org/developers/core-principles/)
- Ensure there are
(tests)[https://www.chromium.org/developers/testing/]. Unit test as much
as possible (including edge cases), but also include browser tests
covering high level functionality.
- Ensure that there are comments explaining what classes/methods are/do.
The "why" is often more important than the "what" in comments. Also
update any relevant docs (moving docs from wiki to brave-core if
necessary).
- Request security or other review (third-party libraries, rust code,
etc...) if applicable [security/privacy review is
needed](https://github.com/brave/brave-browser/wiki/Security-reviews)
[other review](https://github.com/brave/reviews/issues/new/choose)
Also see [adding third-party
libraries](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/adding_to_third_party.md)
for general guidelines on using third party code
- Maks sure there is a
[ticket](https://github.com/brave/brave-browser/issues) for your issue
- Use Github [auto-closing
keywords](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)
in the PR description above
- Write a good [PR/commit
description](https://google.github.io/eng-practices/review/developer/cl-descriptions.html)
- Squash any review feedback or "fixup" commits before merge, so that
history is a record of what happened in the repo, not your PR
- Add appropriate labels (`QA/Yes` or `QA/No`; `release-notes/include`
or `release-notes/exclude`; `OS/...`) to the associated issue
- Checked the PR locally:
* `npm run test -- brave_browser_tests`, `npm run test --
brave_unit_tests`
[wiki](https://github.com/brave/brave-browser/wiki/Tests)
* `npm run presubmit`
[wiki](https://github.com/brave/brave-browser/wiki/Presubmit-checks),
`npm run gn_check`, `npm run tslint`
- Run `git rebase master` (if needed)
-->
2025-09-10 01:14:01 -04:00
..
2025-09-04 07:01:47 -04:00
2025-09-08 07:07:22 -04:00
2025-08-05 18:08:10 +01:00
2025-08-19 19:54:20 +01:00
2025-08-14 15:38:22 -05:00
2025-09-08 13:56:18 -05:00
2025-08-05 18:08:10 +01:00
2025-08-27 17:41:20 -07:00
2025-08-25 16:20:41 +02:00
2025-08-22 08:34:21 -07:00
2025-08-12 16:53:37 -07:00
2025-09-05 14:34:46 -07:00
2025-09-05 17:39:02 +09:00
2025-09-03 10:33:51 +07:00
2025-08-19 19:54:29 +01:00
2025-08-05 18:20:12 +01:00
2025-09-05 17:39:02 +09:00
2025-09-01 18:33:20 +03:00
2025-08-27 04:26:29 +09:00
2025-08-27 20:07:00 +07:00
2025-09-08 11:42:41 -04:00
2025-09-08 15:23:26 -04:00
2025-07-16 13:38:45 -04:00
2025-08-28 17:40:33 +09:00
2025-08-05 18:08:10 +01:00
2025-08-05 18:08:10 +01:00
2025-09-03 19:59:58 +09:00
2025-08-29 02:27:13 +09:00
2025-09-08 12:34:46 -07:00
2025-09-08 12:34:46 -07:00
2025-08-05 18:20:12 +01:00
2025-08-19 19:54:30 +01:00
2025-08-20 01:06:59 +03:00
2025-08-20 01:06:59 +03:00
2025-08-13 11:14:10 -04:00
2025-08-19 19:54:15 +01:00
2025-09-03 20:41:49 -07:00
2025-09-03 20:41:49 -07:00
2025-08-11 14:52:31 -04:00
2025-09-05 13:00:58 +02:00
2025-08-27 08:48:15 -07:00
2025-07-29 13:34:11 -07:00
2025-08-22 19:38:22 +09:00
2025-08-19 19:54:22 +01:00
2025-09-08 20:01:54 -04:00
2025-08-05 18:20:12 +01:00
2025-08-19 19:54:16 +01:00
2025-08-05 18:20:12 +01:00
2025-07-16 13:38:43 -04:00
2025-09-01 20:10:34 +07:00
2025-08-19 19:54:16 +01:00
2025-07-16 13:38:43 -04:00
2025-08-19 19:54:17 +01:00
2025-08-05 18:20:12 +01:00
2025-09-06 00:31:19 +09:00
2025-08-29 17:12:33 +07:00
2025-08-05 18:20:12 +01:00
2025-09-10 12:17:16 +09:00
2025-07-30 18:33:48 +09:00
2025-08-19 19:54:19 +01:00
2025-08-12 20:39:47 -07:00
2025-08-19 19:54:30 +01:00
2025-09-10 12:17:16 +09:00
2025-08-19 15:41:52 -04:00
2025-08-19 15:41:52 -04:00
2025-08-06 15:20:15 -07:00
2025-09-03 19:59:58 +09:00
2025-08-06 14:25:38 +09:00
2025-09-09 17:09:02 -04:00
2025-08-06 07:08:14 -07:00
2025-09-01 20:10:34 +07:00
2025-08-06 08:11:19 -04:00
2025-09-09 18:38:41 -04:00
2025-09-06 00:31:19 +09:00
2025-09-01 20:10:34 +07:00
2025-08-27 17:56:53 +07:00
2025-08-23 05:56:36 +09:00
2025-09-06 16:28:07 -04:00