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

Bump Windows updater to v 1.3.361.121 #12868

Merged
merged 1 commit into from
Apr 4, 2022

Conversation

mherrmann
Copy link
Collaborator

@mherrmann mherrmann commented Apr 4, 2022

This PR had to be reverted. See #12874.

Resolves brave/brave-browser#22060

Testers: This issue has the potential to brick Brave's auto-update fleet on Windows and needs thorough testing. Please see #11096 for a test plan.

Submitter Checklist:

  • I confirm that no security/privacy review is needed, or that I have requested one
  • There is a ticket for my issue
  • Used Github auto-closing keywords in the PR description above
  • Wrote a good PR/commit description
  • Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
  • Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
  • Checked the PR locally: npm run test -- brave_browser_tests, npm run test -- brave_unit_tests, npm run lint, npm run gn_check, npm run tslint
  • Ran git rebase master (if needed)

Reviewer Checklist:

  • A security review is not needed, or a link to one is included in the PR description
  • New files have MPL-2.0 license header
  • Adequate test coverage exists to prevent regressions
  • Major classes, functions and non-trivial code blocks are well-commented
  • Changes in component dependencies are properly reflected in gn
  • Code follows the style guide
  • Test plan is specified in PR before merging

After-merge Checklist:

This contains the following improvements:

1. Disable some statistics collection in Brave's auto-updater on
   Windows.
2. We pulled in the latest changes from Google's upstream implementation
   of the auto-updater. This gives us the latest security and stability
   fixes.
3. We now use Visual Studio 2019 for compiling the auto-updater.
   Previously, we used the less-recommended VS 2017 for building the
   project.
4. We now make sure there are no local changes in the updater sources
   inside Brave's main repository after building. This streamlines other
   parts of Brave's build process such as npm run sync.
5. We made a few other small improvements to the build process of the
   auto-updater. It now gives better error messages and requires fewer
   parameters for a successful build.
@mherrmann mherrmann added CI/skip-android Do not run CI builds for Android CI/skip-linux CI/skip-macos-x64 Do not run CI builds for macOS x64 CI/skip-ios Do not run CI builds for iOS labels Apr 4, 2022
@mherrmann mherrmann added this to the 1.39.x - Nightly milestone Apr 4, 2022
@mherrmann mherrmann requested a review from a team as a code owner April 4, 2022 06:42
@mherrmann mherrmann self-assigned this Apr 4, 2022
@github-actions github-actions bot added the CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) label Apr 4, 2022
@mherrmann mherrmann merged commit 2d974f4 into master Apr 4, 2022
@mherrmann mherrmann deleted the bump-windows-updater-to-v1.3.361.121 branch April 4, 2022 13:14
@mherrmann
Copy link
Collaborator Author

This PR had to be reverted. See #12874.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) CI/skip-android Do not run CI builds for Android CI/skip-ios Do not run CI builds for iOS CI/skip-macos-x64 Do not run CI builds for macOS x64
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bump Brave's Windows updater (Omaha) to v1.3.361.113
3 participants