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 119.0.6045.124 to Chromium 119.0.6045.134. #34209

Closed
mkarolin opened this issue Nov 8, 2023 · 3 comments · Fixed by brave/brave-core#20911
Closed

Upgrade from Chromium 119.0.6045.124 to Chromium 119.0.6045.134. #34209

mkarolin opened this issue Nov 8, 2023 · 3 comments · Fixed by brave/brave-core#20911

Comments

@mkarolin
Copy link
Contributor

mkarolin commented Nov 8, 2023

Minor Chromium bump

https://chromium.googlesource.com/chromium/src/+log/119.0.6045.124..119.0.6045.134?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)
@kjozwiak
Copy link
Member

kjozwiak commented Nov 9, 2023

The above requires 1.60.116 or higher for 1.60.x verification 👍

@Uni-verse
Copy link
Contributor

Verified on Samsung Galaxy S21 using the following version:

Brave	1.60.116 Chromium: 119.0.6045.134 (Official Build) (32-bit) 
Revision	def53af41c7a126b2def06e7f6aa2063ad5364e7
OS	Android 13; Build/TP1A.220624.014; 33; REL
  • Branding items
  • Version bump
Example Example
Screenshot 2023-11-09 at 11 34 46 AM Screenshot 2023-11-09 at 11 35 02 AM

@Uni-verse
Copy link
Contributor

Verified on Samsung Galaxy Tab S7 using the following version:

Brave	1.60.116 Chromium: 119.0.6045.134 (Official Build) (64-bit) 
Revision	def53af41c7a126b2def06e7f6aa2063ad5364e7
OS	Android 13; Build/TP1A.220624.014; 33; REL
  • Version bump
  • Branding
Example Example
Screenshot 2023-11-09 at 12 26 30 PM Screenshot 2023-11-09 at 12 26 51 PM

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

Successfully merging a pull request may close this issue.

4 participants