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.

Sign up for GitHub

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

Jump to bottom

Upgrade from Chromium 130.0.6723.70 to Chromium 130.0.6723.91 (1.72.x) #26296

Merged
merged 2 commits into from
Oct 30, 2024
Merged

Upgrade from Chromium 130.0.6723.70 to Chromium 130.0.6723.91 (1.72.x) #26296

merged 2 commits into from
Oct 30, 2024

Conversation

emerick
Copy link
Contributor

@emerick emerick commented Oct 29, 2024

Resolves brave/brave-browser#41960

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:

@emerick emerick added this to the 1.72.x - Beta milestone Oct 29, 2024
@emerick emerick self-assigned this Oct 29, 2024
@emerick emerick requested a review from a team as a code owner October 29, 2024 22:07
@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) labels Oct 29, 2024
kjozwiak
kjozwiak approved these changes Oct 30, 2024
View reviewed changes
Copy link
Member

@kjozwiak kjozwiak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uplift into 1.72.x approved 👍

@kjozwiak kjozwiak merged commit af8a9b7 into 1.72.x Oct 30, 2024
16 checks passed
@kjozwiak kjozwiak deleted the 130.0.6723.91_1.72.x branch October 30, 2024 02:35
emerick added a commit that referenced this pull request Oct 30, 2024
@emerick @brave-builds
Upgrade from Chromium 130.0.6723.70 to Chromium 130.0.6723.91 (1.72.x) (
176aac3 
#26296)

* Upgrade from Chromium 130.0.6723.70 to Chromium 130.0.6723.91

* Update pins list timestamp

---------

Co-authored-by: brave-builds <brave-builds+devops@brave.com>
@brave-builds
Copy link
Collaborator

Released in v1.72.91

emerick added a commit that referenced this pull request Oct 30, 2024
@emerick @brave-builds
Upgrade from Chromium 130.0.6723.70 to Chromium 130.0.6723.91 (1.72.x) (
d98cae9 
#26296)

* Upgrade from Chromium 130.0.6723.70 to Chromium 130.0.6723.91

* Update pins list timestamp

---------

Co-authored-by: brave-builds <brave-builds+devops@brave.com>
kjozwiak pushed a commit that referenced this pull request Oct 31, 2024
@emerick @brave-builds
@bsclifton @simonhong @samartnik
Upgrade from Chromium 130 to Chromium 131 1.72.x (#26222)
2af1342 
* 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 <brave-builds+devops@brave.com>

* 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 <brave-builds+devops@brave.com>
Co-authored-by: Brian Clifton <brian@clifton.me>
Co-authored-by: Simon Hong <shong@brave.com>
Co-authored-by: Artem Samoilenko <artem@brave.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kjozwiak kjozwiak kjozwiak approved these changes

Assignees

@emerick emerick

Labels
CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) CI/run-network-audit Run network-audit
Projects
None yet
Milestone
1.72.x - Beta
Development

Successfully merging this pull request may close these issues.
3 participants
@emerick @brave-builds @kjozwiak