Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade from Chromium 130 to Chromium 131. #25662

Merged
merged 144 commits into from
Oct 24, 2024
Merged

Upgrade from Chromium 130 to Chromium 131. #25662

merged 144 commits into from
Oct 24, 2024

Conversation

mkarolin
Copy link
Collaborator

Resolves brave/brave-browser#41130

Submitter Checklist:

  • I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
  • There is a ticket for my issue
  • Used Github auto-closing keywords in the PR description above
  • Wrote a good PR/commit description
  • Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
  • Added 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
    • npm run presubmit wiki, npm run gn_check, npm run tslint
  • Ran git rebase master (if needed)

Reviewer Checklist:

  • A security review is not needed, or a link to one is included in the PR description
  • New files have MPL-2.0 license header
  • Adequate test coverage exists to prevent regressions
  • Major classes, functions and non-trivial code blocks are well-commented
  • Changes in component dependencies are properly reflected in gn
  • Code follows the style guide
  • Test plan is specified in PR before merging

After-merge Checklist:

Test Plan:

@github-actions github-actions bot added CI/run-network-audit Run network-audit CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) CI/storybook-url Deploy storybook and provide a unique URL for each build CI/run-upstream-tests Run upstream unit and browser tests on Linux and Windows (otherwise only on Linux) feature/web3/wallet feature/web3/wallet/core labels Sep 19, 2024
@brave-builds
Copy link
Collaborator

A Storybook has been deployed to preview UI for the latest push

mkarolin and others added 13 commits October 24, 2024 12:14
Chromium implementation of DeriveKeyScrypt has a CHECK in it that would
crash the browser if the underlying BoringSSL function failed. We use
this code from HDKey::GenerateFromV3UTC where the data is retrieved from
JSON and can't be guaranteed to always be valid. In order not to crash,
added DeriveKeyScrypt implementation without the CHECK and also changed
our DeriveKeyPbkdf2HmacSha256 implementation to no use CHECK either.

Additionally, moved HDKey::GenerateFromV3UTC code to use DeriveKeyScrypt
and DeriveKeyPbkdf2HmacSha256 directly instead of using SymmetricKey
wrappers that are being deprecated.

Chromium change:
https://chromium.googlesource.com/chromium/src/+/4046edfc95050796d4a1bc54cdba6942257b6f38

commit 4046edfc95050796d4a1bc54cdba6942257b6f38
Author: Elly <[email protected]>
Date:   Thu Oct 10 20:51:36 2024 +0000

    crypto: add kdf interface

    Right now, //crypto supports KDFs via two interfaces:
    * PBKDF2-HMAC-SHA1 and Scrypt on crypto::SymmetricKey
    * HKDF-SHA256 via free functions

    This change:
    * Adds crypto::SubtlePassKey for access to subtle crypto primitives
    * Creates a new KDF interface
    * Moves the PBKDF2-HMAC-SHA1 and Scrypt implementations to that
      interface, and guards them with SubtlePassKeys
    * Adds new unit tests covering those KDFs
    * Deprecates SymmetricKey
    * Deletes many of the unit tests for SymmetricKey, which either covered
      logic which is now moved to the KDF implementations (and is covered by
      their tests) or tested key lengths we don't allow in production.

    Bug: 369653192, 369649346
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/65eee63c0e75ebd343c409a7c14addb00ca4b6dd

[Tab Model] Deprecate tab_groups package

Merge the tab_groups/ package into tabmodel/. The two packages have
significant overlap and should really have a lot of their logic merged
anyway.

This allows us to package protect TabGroupModelFilterInternal and make
destroy method package private as well.

Fixed: 372068933
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/db64d75a6190bc6f3b1014ba0462f391b2b35135

[bookmarks] Fetch favicons from google if they're not found locally

Bug: 368130323,368683034
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/3d4bd05bd10bced9902f9dd06cf1ad19389c6ba2

Add EdgeToEdgeStateProvider to replace usage of #setDecorFitsSystemWindows

Bug: 369841366
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/d15dc67556629c7f39c418cd6b81e03c48eee30c

[UPMAccessLossWarning] Add export flow final step metric

The new metric tracks the last step that the user took as part of the
export flow.

Change-Id: I5db5c776b476c49160b39e3f27ee0a50bd8a4d41
Chromium's last id went up again and was conflicting with our ids
(specifically on MacOS causing a crash constructing Help menu).
As a code review suggestion, split the `if` statement for `doesProcessSuggestion` for better logic readability.`
Page load failes bacause `br_shared_vars.css.js` resource not available for android and ios.

Chromium change:
https://chromium.googlesource.com/chromium/src/+/27af2840dc73c5e5a0cb13e368b2a44820ba7431

FlagsUI: Leverage cr-button instead of a custom button.

As part of this change, several changes are needed to make cr_button.ts
available on Android and iOS builds.

Bug: 40246381
@bsclifton
Copy link
Member

Going to force merge here - we have enough approvals 😄 (was only waiting for one more). We can always fix things in a follow up. QA has signed off (employees can see https://bravesoftware.slack.com/archives/C212VB0RG/p1729802455439579)

@bsclifton bsclifton merged commit 8993dc3 into master Oct 24, 2024
17 checks passed
@bsclifton bsclifton deleted the cr131 branch October 24, 2024 21:14
@github-actions github-actions bot added this to the 1.73.x - Nightly milestone Oct 24, 2024
@brave-builds
Copy link
Collaborator

Released in v1.73.47

emerick pushed a commit that referenced this pull request Oct 25, 2024
Upgrade from Chromium 130 to Chromium 131.
emerick pushed a commit that referenced this pull request Oct 25, 2024
Upgrade from Chromium 130 to Chromium 131.
emerick pushed a commit that referenced this pull request Oct 25, 2024
Upgrade from Chromium 130 to Chromium 131.
emerick pushed a commit that referenced this pull request Oct 30, 2024
Upgrade from Chromium 130 to Chromium 131.
emerick pushed a commit that referenced this pull request Oct 30, 2024
Upgrade from Chromium 130 to Chromium 131.
emerick pushed a commit that referenced this pull request Oct 30, 2024
Upgrade from Chromium 130 to Chromium 131.
kjozwiak pushed a commit that referenced this pull request Oct 31, 2024
* Upgrade from Chromium 130.0.6723.70 to Chromium 130.0.6723.91 (1.72.x) (#26296)

* Upgrade from Chromium 130.0.6723.70 to Chromium 130.0.6723.91

* Update pins list timestamp

---------

Co-authored-by: brave-builds <[email protected]>

* Merge pull request #25662 from brave/cr131

Upgrade from Chromium 130 to Chromium 131.

* Merge pull request #26256 from brave/cr131-followup-fix-extensions-sidebar-styles

Migrate extensions sidebar override to use Lit

* Merge pull request #26277 from brave/cr131-followup-disable-https-first-balanced-mode

Disable HTTPS first balanced mode

* Fixed SearchEngineProviderServiceTest.PRE_InvalidPrivateSearchProviderRestoreTest

fix brave/brave-browser#41470

TemplateURLService should be loaded before setting
prefs::kSyncedDefaultPrivateSearchProviderGUID prefs.

* [Android] Fix for crash in Password settings

Chromium change:
https://source.chromium.org/chromium/chromium/src/+/df77cbacb9476b0b6d3e75cc34b5d127985e79c3

[Settings] Enable the single-activity mode by default

Bug: b/356743945

* [Android] Explicitly remove `New tab page cards` from menu

This item used in the upstream NTP, that we don't use.

---------

Co-authored-by: brave-builds <[email protected]>
Co-authored-by: Brian Clifton <[email protected]>
Co-authored-by: Simon Hong <[email protected]>
Co-authored-by: Artem Samoilenko <[email protected]>
@bsclifton bsclifton modified the milestones: 1.73.x - Nightly, 1.74.x - Nightly Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) CI/run-network-audit Run network-audit CI/run-upstream-tests Run upstream unit and browser tests on Linux and Windows (otherwise only on Linux) CI/storybook-url Deploy storybook and provide a unique URL for each build feature/web3/wallet/core feature/web3/wallet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade from Chromium 130 to Chromium 131