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 102 to Chromium 103 (1.40.x) #13755

Merged
merged 4 commits into from
Jun 16, 2022
Merged

Upgrade from Chromium 102 to Chromium 103 (1.40.x) #13755

merged 4 commits into from
Jun 16, 2022

Conversation

emerick
Copy link
Contributor

@emerick emerick commented Jun 13, 2022 •
edited
Loading

Resolves brave/brave-browser#22804
Uplift from #13331

Also includes following reggression fixes:

Submitter Checklist:

  • I confirm that no security/privacy review is needed, or that I have requested one
  • 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, npm run lint, 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.40.x - Beta milestone Jun 13, 2022
@emerick emerick requested a review from a team June 13, 2022 15:43
@emerick emerick self-assigned this Jun 13, 2022
@emerick emerick requested review from a team as code owners June 13, 2022 15:43
@github-actions github-actions bot added CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) CI/run-network-audit Run network-audit CI/storybook-url Deploy storybook and provide a unique URL for each build potential-layer-violation-fixes This PR touches a BUILD.gn file with check_includes=false labels Jun 13, 2022
@brave-builds
Copy link
Collaborator

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

@brave-builds
Copy link
Collaborator

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

@emerick emerick force-pushed the cr103-1.40.x branch 2 times, most recently from 7749d27 to 995eedd Compare June 13, 2022 19:25
@brave-builds
Copy link
Collaborator

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

@brave-builds
Copy link
Collaborator

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

@brave-builds
Copy link
Collaborator

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

kjozwiak
kjozwiak approved these changes Jun 15, 2022
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.40.x approved 👍

@kjozwiak kjozwiak self-requested a review June 15, 2022 21:21
emerick and others added 4 commits June 15, 2022 17:28
@emerick
Merge pull request #13331 from brave/cr103
085b6bb
@simonhong @emerick
Merge pull request #13746 from brave/default_browser_prompt_dialog_bg…
4e4187c 
…_color

Fixed wrong background color of default browser prompt dialog
@samartnik @emerick
Merge pull request #13772 from brave/android_disable_speculation_rules
31c762d 
Fixes error thrown when speculation rules are disabled
@emerick
Merge pull request #13775 from brave/fix-tor-proxy-task-runner
7ee4a93 
Fix browser crash when setting new Tor connection circuit
@brave-builds
Copy link
Collaborator

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

kjozwiak
kjozwiak approved these changes Jun 16, 2022
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.40.x approved 👍

@kjozwiak kjozwiak merged commit 3f74cc1 into 1.40.x Jun 16, 2022
@kjozwiak kjozwiak deleted the cr103-1.40.x branch June 16, 2022 06:40
This was referenced Jun 16, 2022
Closed
Closed
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

@samartnik samartnik Awaiting requested review from samartnik samartnik is a code owner

@iefremov iefremov Awaiting requested review from iefremov iefremov is a code owner

@simonhong simonhong Awaiting requested review from simonhong simonhong is a code owner

Assignees

@emerick emerick

Labels
CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) CI/run-network-audit Run network-audit CI/storybook-url Deploy storybook and provide a unique URL for each build potential-layer-violation-fixes This PR touches a BUILD.gn file with check_includes=false
Projects
None yet
Milestone
1.40.x - Release
5 participants
@emerick @brave-builds @kjozwiak @simonhong @samartnik