-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Brave Release Schedule
- Overview
- Current channel information
- Current build schedule
- Release channel dates
- Beta channel migration dates
- Nightly channel migration dates
- Mobile platforms
- How to do branch migrations
Currently published version numbers can be seen at https://versions.brave.com/
- Major Release frequency: ~3 weeks
- Minor Chromium/Security releases: Every Tuesday (within ~24hrs after released) as per Chromium schedule. (however, these are tentative and subject to change)
- Chemspill/Hotfix frequency: As needed
- Every major release is tied to a fuzzy Chromium release date.
Older Brave Release Schedules are available in the Brave Release Schedules Archive.
Information about channel differences available in the Release Channel Descriptions.
| Channel | Release | Beta | Nightly |
|---|---|---|---|
| Milestone | 1.73.x | 1.74.x | 1.75.x |
| Branch name | 1.73.x | 1.74.x | master |
Note: These versions represent which channel our CI builds things on. It may not reflect exactly the version on release channel for example. 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.
The following is our automated schedule for creating and uploading builds to our Sparkle (macOS), Omaha (Windows) servers and our Linux repositories.
| Channel | Time | Days | Platforms | Public |
|---|---|---|---|---|
Beta |
4am UTC (8pm PST/11pm EST) | Monday, Wednesday, Friday | android linux-x64 macos-x64 macos-arm64 windows-x64 | no |
Beta |
4am UTC (8pm PST/11pm EST) | Tuesday, Thursday | all | yes |
Nightly |
12pm UTC (4am PST/7am EST) | Monday - Friday | all | yes |
Nightly |
4pm UTC (8am PST/11am EST) | Monday - Friday | android linux-x64 macos-x64 macos-arm64 windows-x64 | no |
Nightly |
12am UTC (4pm PST/7pm EST) | Monday - Friday | android linux-x64 macos-x64 macos-arm64 windows-x64 | no |
| Version | Chromium | Migration Date | Release Date | Comments |
|---|---|---|---|---|
| 1.70.x | 129 | September 11, 2024 | September 19, 2024 | Release delayed. Originally scheduled to release on September 17, 2024. |
| 1.71.x | 130 | October 9, 2024 | October 17, 2024 | Release delayed. Originally scheduled to release on October 15, 2024. |
| 1.72.x | N/A | N/A | N/A | https://community.brave.com/t/channel-migrations-update/579281 |
| 1.73.x | 131 | November 6, 2024 | November 12, 2024 | |
| 1.74.x | 132 | December 11, 2024 | January 7, 2025 | |
| 1.75.x | 133 | January 29, 2025 | February 4, 2025 | |
| 1.76.x | 134 | February 26, 2025 | March 4, 2025 | |
| 1.77.x | 135 | March 26, 2025 | April 1, 2025 | |
| 1.78.x | 136 | April 23, 2025 | April 29, 2025 | |
| 1.79.x | 137 | May 21, 2025 | May 27, 2025 | |
| 1.80.x | 138 | June 18, 2025 | June 24, 2025 | |
| 1.81.x | 139 | July 30, 2025 | August 5, 2025 | |
| 1.82.x | 140 | August 27, 2025 | September 2, 2025 | |
| 1.83.x | 141 | September 24, 2025 | September 30, 2025 | |
| 1.84.x | 142 | October 22, 2025 | October 28, 2025 | |
| 1.85.x | 143 | November 19, 2025 | December 2, 2025 |
Note: As announced via https://security.googleblog.com/2023/08/an-update-on-chrome-security-updates.html, we'll be getting minor chromium bumps every Tuesday. These releases will sometime also include P1 & P2 issues that are deemed important enough to get out ASAP rather than waiting for a major release. For example, HackerOne reports or other issues that are affecting users in a major way.
- All dates are approximate and are subject to change.
-
Maintenance releasesare tentative and subject to change. -
Migration Dateis also the cutoff date to add strings that need to be translated for the release. - Updates will be released as requested only.
| Version | # of days between releases | Comments |
|---|---|---|
| 1.70.x - 1.71.x | 28 days | |
| 1.71.x - 1.73.x | 28 days | |
| 1.73.x - 1.74.x | 56 days | |
| 1.74.x - 1.75.x | 28 days | |
| 1.75.x - 1.76.x | 28 days | |
| 1.76.x - 1.77.x | 28 days | |
| 1.77.x - 1.78.x | 28 days | |
| 1.78.x - 1.79.x | 28 days | |
| 1.79.x - 1.80.x | 28 days | |
| 1.80.x - 1.81.x | 42 days | |
| 1.81.x - 1.82.x | 28 days | |
| 1.82.x - 1.83.x | 28 days | |
| 1.83.x - 1.84.x | 28 days | |
| 1.84.x - 1.85.x | 35 days |
| Version | Target Chromium | Migration Date | Comments |
|---|---|---|---|
| 1.70.x | 129 | August 14, 2024 | |
| 1.71.x | 130 | September 11, 2024 | |
| 1.72.x | 131 | October 9, 2024 | |
| 1.73.x | N/A | N/A | https://community.brave.com/t/channel-migrations-update/579281 |
| 1.74.x | 132 | November 6, 2024 | |
| 1.75.x | 133 | December 11, 2024 | |
| 1.76.x | 134 | January 29, 2025 | |
| 1.77.x | 135 | February 26, 2025 | |
| 1.78.x | 136 | March 26, 2025 | |
| 1.79.x | 137 | April 23, 2025 | |
| 1.80.x | 138 | May 21, 2025 | |
| 1.81.x | 139 | June 18, 2025 | |
| 1.82.x | 140 | July 30, 2025 | |
| 1.83.x | 141 | August 27, 2025 | |
| 1.84.x | 142 | September 24, 2025 | |
| 1.85.x | 143 | October 22, 2025 | |
| 1.86.x | 144 | November 19, 2025 |
- CI does builds for Beta channel happen twice a week.
- Updates are released as there are builds as long as tests pass.
| Version | Target Chromium | Migration Date | Comments |
|---|---|---|---|
| 1.70.x | 129 | July 17, 2024 | |
| 1.71.x | 130 | August 14, 2024 | |
| 1.72.x | 131 | September 11, 2024 | |
| 1.73.x | 132 | October 9, 2024 | |
| 1.74.x | N/A | N/A | https://community.brave.com/t/channel-migrations-update/579281 |
| 1.75.x | 133 | November 6, 2024 | |
| 1.76.x | 134 | December 11, 2024 | |
| 1.77.x | 135 | January 29, 2025 | |
| 1.78.x | 136 | February 26, 2025 | |
| 1.79.x | 137 | March 26, 2025 | |
| 1.80.x | 138 | April 23, 2025 | |
| 1.81.x | 139 | May 21, 2025 | |
| 1.82.x | 140 | June 18, 2025 | |
| 1.83.x | 141 | July 30, 2025 | |
| 1.84.x | 142 | August 27, 2025 | |
| 1.85.x | 143 | September 24, 2025 | |
| 1.86.x | 144 | October 22, 2025 | |
| 1.87.x | 145 | November 19, 2025 |
- Nightly builds will be made from master for this channel.
- This means that within a day of any change you can start testing it.
- Developers work off of master.
- We keep master stable, when it is not, we backout what broke it.
- If something fails tests, that thing should be backed out.
-
brave/brave-browser'spackage.jsonspecifies brave-core branch to bemaster.
When 1) approved in the Google Play Store and 2) QA has signed off on the release, we'll release in a staged rollout. Before moving to the next stage, crash reports are checked by release team and evaluated.
Assuming we have the release ready in the morning, the schedule will typically look like this:
| day | time | rollout |
|---|---|---|
| 1 | morning | initial release 1% |
| 1 | evening | 5% |
| 2 | morning | 10% |
| 2 | evening | 20% |
| 3 | morning | 50% |
| 3 | evening | 100% |
When 1) approved in iOS App Store and 2) QA has signed off on the release, we'll begin the automated rollout. This takes place over 7 days to people who have automatic updates enabled. Users can visit the App Store page for Brave at any time and get the latest one
If something goes wrong, the release can be paused.
| day | rollout |
|---|---|
| 1 | initial release 1% |
| 2 | 2% |
| 3 | 5% |
| 4 | 10% |
| 5 | 20% |
| 6 | 50% |
| 7 | 100% |
- Visit https://ci.brave.com/job/branch-migrations/
- Queue the job
- Verify results
For folks that want to see more of "how the sausage is made" (link restricted to Brave employees), you can view the Jenkins job details here: https://github.com/brave/devops/blob/master/jenkins/jobs/browser/branch-migrations.yml