Skip to content

Upgrade from Chromium 76.0.3809.132 to Chromium 77.0.3865.75 (uplift to 0.68.x)#5943

Merged
bsclifton merged 7 commits into0.68.xfrom
c77_0.68.x
Sep 11, 2019
Merged

Upgrade from Chromium 76.0.3809.132 to Chromium 77.0.3865.75 (uplift to 0.68.x)#5943
bsclifton merged 7 commits into0.68.xfrom
c77_0.68.x

Conversation

@bsclifton
Copy link
Member

@bsclifton bsclifton commented Sep 9, 2019

Uplift of #5896 and #5967
Fixes #5375
Fixes #5966
Related brave/brave-core#3385

Approved, please ensure that before merging:

  • You have checked CI and the builds, lint, and tests all pass or are not related to your PR.
  • You have tested your change on Nightly.
  • The PR milestones match the branch they are landing to.

After you merge:

  • The associated issue milestone is set to the smallest version that the changes is landed on.

Upgrade from Chromium 76.0.3809.132 to Chromium 77.0.3865.65
@bsclifton bsclifton self-assigned this Sep 9, 2019
@bsclifton bsclifton added this to the 0.68.x - Release Hotfix 2 milestone Sep 9, 2019
@bsclifton bsclifton removed the CI/skip label Sep 9, 2019
@bsclifton bsclifton changed the title WIP - uplifting C77 to 0.68.x Upgrade from Chromium 76.0.3809.132 to Chromium 77.0.3865.65 (0.68.x) Sep 11, 2019
@bsclifton bsclifton changed the title Upgrade from Chromium 76.0.3809.132 to Chromium 77.0.3865.65 (0.68.x) Upgrade from Chromium 76.0.3809.132 to Chromium 77.0.3865.75 (Uplift to 0.68.x) Sep 11, 2019
@bsclifton bsclifton changed the title Upgrade from Chromium 76.0.3809.132 to Chromium 77.0.3865.75 (Uplift to 0.68.x) Upgrade from Chromium 76.0.3809.132 to Chromium 77.0.3865.75 (uplift to 0.68.x) Sep 11, 2019
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 0.68.x approved. Please make sure that all the correct labels are being used and all associated issues that are relevant to this PR are moved into the correct milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants