When 1) approved in the Google Play Store and 2) QA has signed off on the release, we'll release in a staged rollout.

brave/brave-browser's package.json specifies brave-core branch to be master.

If something fails tests, that thing should be backed out.

We keep master stable, when it is not, we backout what broke it.

This means that within a day of any change you can start testing it.

Nightly builds will be made from master for this channel.

Updates are released as there are builds as long as tests pass.

CI builds for Dev channel happen once a day on weekdays.

CI does builds for Beta channel happen twice a week.

Number of days between each release on Release channel Versionīeta & Dev channel migration dates: Version

Updates will be released as requested only.

Migration Date is also the cutoff date to add strings that need to be translated for the release.

Maintenance releases are tentative and subject to change.All dates are approximate and are subject to change.Maintenance Release (tentative) - Note: Depending on QA availability, this maintenance release may be moved to January 4, 2023 Linux-圆4 macos-圆4 macos-arm64 win64 win32 The following is our automated schedule for creating and uploading builds to our Sparkle (macOS), Omaha (Windows) servers and our Linux repositories. This would happen if for example Release above said 0.58.x and it was in RC but on our website we still offered 0.57.x. It may not reflect exactly the version on release channel for example.

Note: These versions represent which channel our CI builds things on. Information about channel differences available in the Release Channel Descriptions. Older Brave Release Schedules are available in the Brave Release Schedules Archive. Every major release is tied to a fuzzy Chromium release date.Maintenance Release frequency: ~2 weeks after a major release (however, these are tentative and subject to change).Currently published version numbers can be seen at

Brave 2 the time machine release date