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 133 to Chromium 134 #43213

Open
emerick opened this issue Jan 9, 2025 · 0 comments · May be fixed by brave/brave-core#27172
Open

Upgrade from Chromium 133 to Chromium 134 #43213

emerick opened this issue Jan 9, 2025 · 0 comments · May be fixed by brave/brave-core#27172
Assignees
@emerick @AlexeyBarabash @cdesouza-chromium
Labels
OS/Android Fixes related to Android browser functionality OS/Desktop OS/iOS Fixes related to iOS browser functionality QA/Test-Plan-Specified QA/Yes release-notes/exclude

Comments

@emerick
Copy link
Contributor

emerick commented Jan 9, 2025

Description

Description

Upgrade from Chromium 133 to Chromium 134

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

QA tests:
This is a major Chromium version bump, please do full passes.

Desktop Affected areas:

  • TBD

iOS Affected areas:

  • TBD

Android Affected areas:

  • TBD
@emerick emerick added OS/Android Fixes related to Android browser functionality OS/Desktop OS/iOS Fixes related to iOS browser functionality QA/Test-Plan-Specified QA/Yes release-notes/exclude labels Jan 9, 2025
@emerick emerick linked a pull request Jan 9, 2025 that will close this issue
Draft
24 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@emerick emerick

@AlexeyBarabash AlexeyBarabash

@cdesouza-chromium cdesouza-chromium

Labels
OS/Android Fixes related to Android browser functionality OS/Desktop OS/iOS Fixes related to iOS browser functionality QA/Test-Plan-Specified QA/Yes release-notes/exclude
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upgrade from Chromium 133 to Chromium 134 brave/brave-core
3 participants
@emerick @AlexeyBarabash @cdesouza-chromium