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 110.0.5481.97 to Chromium 110.0.5481.100 (1.48.x) #17231

Merged
merged 1 commit into from
Feb 15, 2023
Merged

Upgrade from Chromium 110.0.5481.97 to Chromium 110.0.5481.100 (1.48.x) #17231

merged 1 commit into from
Feb 15, 2023

Conversation

emerick
Copy link
Contributor

@emerick emerick commented Feb 15, 2023

Resolves brave/brave-browser#28515

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 @brave-builds
Upgrade from Chromium 110.0.5481.97 to Chromium 110.0.5481.100 (1.48.…
b8d8c06 
…release4) (#17209)

* Upgrade from Chromium 110.0.5481.97 to Chromium 110.0.5481.100

* Upgrade patches from Chromium 110.0.5481.97 to Chromium 110.0.5481.100

* Update pins list timestamp

---------

Co-authored-by: brave-builds <brave-builds+devops@brave.com>
@emerick emerick added this to the 1.48.x - Release #3 milestone Feb 15, 2023
@emerick emerick self-assigned this Feb 15, 2023
@emerick emerick requested a review from a team as a code owner February 15, 2023 12:08
@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 Feb 15, 2023
kjozwiak
kjozwiak approved these changes Feb 15, 2023
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.48.x approved 👍

@kjozwiak kjozwiak merged commit 775f115 into 1.48.x Feb 15, 2023
@kjozwiak kjozwiak deleted the 1.48.x-release4-merge branch February 15, 2023 18:37
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.48.x - Release #5
Development

Successfully merging this pull request may close these issues.
2 participants
@emerick @kjozwiak