-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Upgrade from Chromium 99.0.4844.83 to Chromium 99.0.4844.88. #21889
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
Comments
Verification passed on
|
Verification passed on
|
Sorry, is this right calling this a minor Chromium bump @mkarolin ? See the emergency security update on Chrome https://chromereleases.googleblog.com/2022/03/stable-channel-update-for-desktop_25.html Thanks, |
@mickthegrit I believe minor here may refer to the version-number change, rather than the severity of the issue addressed. Note, we went from version 99.0.4844.83 to 99.0.4844.84. |
What @jonathansampson captured is right 😄 This is a "minor version update" in that it's not updating the major version (ex: Chromium 99 => Chromium 100). Most minor updates include good security fixes that we need to include - this bump is critical as it fixes a very high severity issue. Thanks for asking @mickthegrit. Sorry for the semantics here |
Hi, why my Brave browser tells me it's still up to date, while in fact it's not. I still have the following: Thanks for your help. |
@faxotherapy Which OS/version are you using? |
MacOS Mojave 10.14.6 |
Minor Chromium bump.
https://chromium.googlesource.com/chromium/src/+log/99.0.4844.83..99.0.4844.88?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).
The text was updated successfully, but these errors were encountered: