-
Notifications
You must be signed in to change notification settings - Fork 888
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
Pulled l10n for 1.37.x release (Chromium 100). Part II. #12957
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This l10n pull also resolves brave/brave-browser#21808. You might like to include it in your description so merging will close the issue 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
++
@mkarolin assuming we'll want this in the
|
aaad511
to
1d50b65
Compare
1d50b65
to
a7a310b
Compare
Windows CI failed in an unrelated browser test ( |
Pulled l10n for 1.37.x release (Chromium 100). Part II.
Pulled l10n for 1.37.x release (Chromium 100). Part II.
Fixes brave/brave-browser#22185
Fixes brave/brave-browser#21808
Fixes brave/brave-browser#21980
Fixes brave/brave-browser#22104
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
,npm run lint
,npm run gn_check
,npm run tslint
git rebase master
(if needed)Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on
Test Plan: