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 112.0.5615.29 to Chromium 112.0.5615.39 #17741

Merged
merged 3 commits into from
Mar 24, 2023

Conversation

emerick
Copy link
Contributor

@emerick emerick commented Mar 23, 2023

Resolves brave/brave-browser#29277

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 wiki
    • npm run lint, 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.51.x - Nightly milestone Mar 23, 2023
@emerick emerick requested a review from a team March 23, 2023 19:20
@emerick emerick self-assigned this Mar 23, 2023
@emerick emerick requested review from a team as code owners March 23, 2023 19:20
@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 labels Mar 23, 2023
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.

LGTM 👍

@kjozwiak kjozwiak merged commit 63857bf into master Mar 24, 2023
@kjozwiak kjozwiak deleted the 112.0.5615.39_master branch March 24, 2023 20:35
emerick added a commit that referenced this pull request Mar 24, 2023
* Upgrade from Chromium 112.0.5615.29 to Chromium 112.0.5615.39

* Upgrade patches from Chromium 112.0.5615.29 to Chromium 112.0.5615.39

* Update pins list timestamp

---------

Co-authored-by: brave-builds <brave-builds+devops@brave.com>
kjozwiak pushed a commit that referenced this pull request Mar 27, 2023
* Merge pull request #17187 from brave/cr112

Upgrade from Chromium 111 to Chromium 112.

* Merge pull request #17675 from brave/android_fix_mapping_file_check

[Android] [C112] Fix for mapping file check

* Upgrade from Chromium 112.0.5615.29 to Chromium 112.0.5615.39 (#17741)

* Upgrade from Chromium 112.0.5615.29 to Chromium 112.0.5615.39

* Upgrade patches from Chromium 112.0.5615.29 to Chromium 112.0.5615.39

* Update pins list timestamp

---------

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

---------

Co-authored-by: samartnik <30602739+samartnik@users.noreply.github.com>
Co-authored-by: Emerick Rogul <erogul@brave.com>
Co-authored-by: brave-builds <brave-builds+devops@brave.com>
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade from Chromium 112.0.5615.29 to Chromium 112.0.5615.39
3 participants