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 104.0.5112.81 to Chromium 104.0.5112.102 (1.43.x). #14666

Merged
merged 2 commits into from
Aug 17, 2022
Merged

Upgrade from Chromium 104.0.5112.81 to Chromium 104.0.5112.102 (1.43.x). #14666

merged 2 commits into from
Aug 17, 2022

Conversation

mkarolin
Copy link
Collaborator

@mkarolin mkarolin commented Aug 16, 2022 •
edited by kjozwiak
Loading

Fixes brave/brave-browser#24713

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:

@mkarolin mkarolin added CI/run-network-audit Run network-audit CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) labels Aug 16, 2022
@mkarolin mkarolin requested a review from a team as a code owner August 16, 2022 22:26
@mkarolin mkarolin self-assigned this Aug 16, 2022
@mkarolin mkarolin added this to the 1.43.x - Beta milestone Aug 16, 2022
kjozwiak
kjozwiak approved these changes Aug 17, 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.43.x approved 👍

@kjozwiak kjozwiak merged commit 4290af0 into 1.43.x Aug 17, 2022
@kjozwiak kjozwiak deleted the 104.0.5112.102_1.43.x branch August 17, 2022 07:25
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

@mkarolin mkarolin

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.43.x - Release
Development

Successfully merging this pull request may close these issues.
3 participants
@mkarolin @kjozwiak @brave-browser-releases