Skip to content

Brave Release Schedule

Jump to bottom
Kamil Jozwiak edited this page Oct 27, 2025 · 483 revisions

TOC

Overview

Currently published version numbers can be seen at https://versions.brave.com/

  • Major Release frequency: ~3 weeks based on the Brave release schedule.
  • Minor Chromium/Security releases: ~once a week on all channels. Within ~24hrs on the release channel after a new Chromium as been released as per the weekly Chromium schedule.
  • 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.

Current channel information:

Channel Release Beta Nightly
Milestone 1.84.x 1.85.x 1.86.x
Branch name 1.84.x 1.85.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.

Current build schedule:

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 04:00 UTC (8pm PST/11pm EST) Monday, Wednesday, Friday android linux-x64 macos-x64 macos-arm64 windows-x64 no
Beta 04:00 UTC (8pm PST/11pm EST) Tuesday, Thursday all yes
Nightly 12:00 UTC (4am PST/7am EST) Monday - Friday all, except android yes
Nightly 12:00 UTC (4am PST/7am EST) Monday, Thursday android yes
Nightly 12:00 UTC (4am PST/7am EST) Tuesday, Wednesday, Friday android no
Nightly 16:00 UTC (8am PST/11am EST) Monday - Friday android linux-x64 macos-x64 macos-arm64 windows-x64 no
Nightly 00:00 UTC (4pm PST/7pm EST) Monday - Friday android linux-x64 macos-x64 macos-arm64 windows-x64 no

Release channel dates:

Version Chromium Migration Date Release Date Comments
1.83.x 141 September 24, 2025 October 2, 2025 Release delayed. Originally scheduled to release on September 30, 2025.
1.84.x 142 October 22, 2025 October 29, 2025 Release delayed. Originally scheduled to release on October 28, 2025.
1.85.x 143 November 19, 2025 December 2, 2025
1.86.x 144 January 7, 2026 January 13, 2026
1.87.x 145 February 4, 2026 February 10, 2026
1.88.x 146 March 4, 2026 March 10, 2026
1.89.x 147 April 1, 2026 April 7, 2026
1.90.x 148 April 29, 2026 May 5, 2026
1.91.x 149 May 27, 2026 June 2, 2026
1.92.x 150 June 24, 2026 June 30, 2026
1.93.x 151 July 22, 2026 July 28, 2026
1.94.x 152 August 19, 2026 August 25, 2026
1.95.x 153 September 16, 2026 September 22, 2026
1.96.x 154 October 14, 2026 October 20, 2026
1.97.x 155 November 11, 2026 November 17, 2026
1.98.x 156 December 16, 2026 January 5, 2027

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.
  • Migration Date is also the cutoff date to add strings that need to be translated for the release.
  • Updates will be released as requested only.
  • Brave releases tend to be on Wednesday's rather than Chromium's Tuesday releases. This is because we usually need to wait and see what version of Chromium Chrome releases with. Sometimes it's a newer version that hasn't yet been announced via https://chromereleases.googleblog.com so we need to update Brave and create new release candidates (RC) builds which usually takes the entire day. Hence releasing the new Chromium on Wednesday rather than Tuesday. We always want to be on the same Chromium version as Chrome.

Number of days between each release on Release channel

Version # of days between releases Comments
1.82.x - 1.83.x 28 days
1.83.x - 1.84.x 28 days
1.84.x - 1.85.x 35 days
1.85.x - 1.86.x 42 days
1.86.x - 1.87.x 28 days
1.87.x - 1.88.x 28 days
1.88.x - 1.89.x 28 days
1.89.x - 1.90.x 28 days
1.90.x - 1.91.x 28 days
1.91.x - 1.92.x 28 days
1.92.x - 1.93.x 28 days
1.93.x - 1.94.x 28 days
1.94.x - 1.95.x 28 days
1.95.x - 1.96.x 28 days
1.96.x - 1.97.x 28 days
1.97.x - 1.98.x 49 days

Beta channel migration dates:

Version Target Chromium Migration Date Comments
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
1.87.x 145 January 7, 2026
1.88.x 146 February 4, 2026
1.89.x 147 March 4, 2026
1.90.x 148 April 1, 2026
1.91.x 149 April 29, 2026
1.92.x 150 May 27, 2026
1.93.x 151 June 24, 2026
1.94.x 152 July 22, 2026
1.95.x 153 August 19, 2026
1.96.x 154 September 16, 2026
1.97.x 155 October 14, 2026
1.98.x 156 November 11, 2026
1.99.x 157 December 16, 2026
  • CI does builds for Beta channel happen twice a week.
  • Updates are released as there are builds as long as tests pass.

Nightly channel migration dates:

Version Target Chromium Migration Date Comments
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
1.88.x 146 January 7, 2026
1.89.x 147 February 4, 2026
1.90.x 148 March 4, 2026
1.91.x 149 April 1, 2026
1.92.x 150 April 29, 2026
1.93.x 151 May 27, 2026
1.94.x 152 June 24, 2026
1.95.x 153 July 22, 2026
1.96.x 154 August 19, 2026
1.97.x 155 September 16, 2026
1.98.x 156 October 14, 2026
1.99.x 157 November 11, 2026
1.100.x 158 December 16, 2026
  • 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's package.json specifies brave-core branch to be master.

Mobile platforms

Android rollout process

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%

iOS rollout process

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%

How to do branch migrations:

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

Clone this wiki locally