Upload Windows stub and silent installer to S3 bucket using similar command to Mac dmg above (i.e BraveBrowserSetup.exe, BraveBrowserSetup32.exe, BraveBrowserSilentSetup.exe, BraveBrowserSilentSetup32.exe).

Brave-Browser-Dev.dmg s3://brave-browser-downloads/latest/Brave-Browser-Dev.dmg -acl public-read)

Sign Linux builds and upload to S3 repositories.

Upload Mac/Win build to Omaha production channels ( x86-rel, 圆4-rel, stable(mac)).

Publish GitHub release (remove 'pre-release' checkmark).

QA summary and sign off report under #release via Slack.

Install a prior version of Brave and update via test channels ( 86-r-test, 64-r-test, test(macOS)).

Log into Fastly, clear CDN cache for:,.

Upload builds to Omaha test channels ( 86-r-test, 64-r-test, test(mac)).

Commit release notes to CHANGELOG_DESKTOP.md in brave-browser master branch, must be completed before release to production Jenkins build job is run.

Mark closed issues in GitHub as release-notes/exclude or release-notes/include.

In these cases, ensure that BETA also goes out within ~24hrs. This leaves users vulnerable and doesn't respect our 1-day SLA promise.

When this happens, users need to wait until Tuesday, when the next public BETA build is pushed out. This is a quick check to avoid cases where a zero-day chromium bump was merged late on Thursday, missing the public build as per. When pushing out a chromium bump (especially a zero-day chromium release), ensure that BETA builds have also been started/pushed publicly.Nightly & BETA channels (HF/zero-day chromium releases) Consult with PR team and provide heads-up on release timing, screenshots, and other deliverables.Release using the critical feature (forces users to update/restart) if there's a zero-day vulnerability being exploited.Consult with the security team to ensure that all security issues have been included.

Ensure that the RC executable installs/launches without any issues on x86 platforms ( Note: preferably all three are checked but one should be good enough if others can't be checked).Note: If there's issues that need to be checked, create a master GH issue that lists the issues that need to be QA'd.Double check the previous release/milestone and ensure everything has been QA'd.Feel free to copy this into an issue if you want to keep track of items per-milestone.īe super sure that is replaced with the version you wish to use.

Instal brave 1.58.137