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 91.0.4472.38 to Chromium 91.0.4472.57. #15800

Closed
mkarolin opened this issue May 12, 2021 · 4 comments · Fixed by brave/brave-core#8793 or #15816
Closed

Upgrade from Chromium 91.0.4472.38 to Chromium 91.0.4472.57. #15800

mkarolin opened this issue May 12, 2021 · 4 comments · Fixed by brave/brave-core#8793 or #15816

Comments

@mkarolin
Copy link
Contributor

Minor Chromium bump.

https://chromium.googlesource.com/chromium/src/+log/91.0.4472.38..91.0.4472.57?pretty=fuller&n=10000

QA tests:

Check branding items
Check for version bump

Additional checks:

No specific code changes in Brave (only line number changes in patches).

@stephendonner
Copy link

Version bump is fine, but @LaurenWags found #15870, which is likely due to this, per @mkarolin

@stephendonner
Copy link

Verified PASSED using

Brave 1.26.22 Chromium: 91.0.4472.57 (Official Build) nightly (64-bit)
Revision e3443317fa07f1e9997e4a9c738eddfefc3c0292-refs/branch-heads/4472_54@{#6}
OS Windows 10 OS Version 2009 (Build 21382.1)
brave://version brave://settings/help
version about-branding

@kjozwiak
Copy link
Member

@brave/legacy_qa just a heads up, this issue will be replaced by #15973 once it lands into master and is uplifted into 1.25.x & 1.26.x. We can start running through the manual passes once we get a 1.25.x RC even it doesn't have #15973. We'll just run through a quick spot check.

@srirambv
Copy link
Contributor

Verification passed on the following devices running 1.25.65

OnePlus 6T (Android 10) Samsung Tab A (Android 10)

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