Electron Releases

Electron frequently releases major versions alongside every other Chromium release. This document focuses on the release cadence and version support policy.

[!TIP] See the Electron Versioning document for more details on how Electron is versioned.

Timeline

Electron's Release Schedule lists a schedule of Electron major releases showing key milestones including alpha, beta, and stable release dates, as well as end-of-life dates and dependency versions.

[!IMPORTANT] Electron's official support policy is the latest 3 stable releases. Our stable release and end-of-life dates are determined by Chromium, and may be subject to change. While we try to keep our planned release and end-of-life dates frequently updated here, future dates may change if affected by upstream scheduling changes, and may not always be accurately reflected.

See Chromium's public release schedule for definitive information about Chromium's scheduled release dates.

Electron's cadence between major version releases is 8 weeks long. Before each major version hits stable, it goes through a four-week alpha phase and a four-week beta phase.

mermaid

gantt
    title Electron release cycle
    dateFormat  YYYY-MM-DD
    axisFormat  Week %W
    todayMarker off
    section v41
    Alpha phase                    :a1, 2026-01-19, 4w
    M146 enters Chrome beta        :milestone, bm1, after a1, 0d
    Beta phase                     :b1, after a1, 4w
    M146 enters Chrome stable      :milestone, s1, after b1, 0d
    Supported until v44 release    :active, after b1, 12w
    section v42
    Alpha phase                    :a2, after b1, 4w
    M148 enters Chrome beta        :milestone, bm2, after a2, 0d
    Beta phase                     :b2, after a2, 4w
    M148 enters Chrome stable      :milestone, s2, after b2, 0d
    Supported until v45 release    :active, after b2, 4w

Notes:

Alphas are generally less stable than beta releases. The cutoff between the two corresponds to when the underlying Chromium version enters Chrome's Beta channel.
The -alpha.1, -beta.1, and stable dates are our solid release dates.
We strive for weekly alpha/beta releases, but we often release more than scheduled.
All dates are our goals but there may be reasons for adjusting the stable deadline, such as security bugs.

Historical changes:

Since Electron 5, Electron has been publicizing its release dates (see blog post).
Since Electron 6, Electron major versions have been targeting every other Chromium major version. Each Electron stable should happen on the same day as Chrome stable (see blog post).
Since Electron 16, Electron has been releasing major versions on an 8-week cadence in accordance to Chrome's change to a 4-week release cadence (see blog post).
Electron temporarily extended support for Electron 22 until October 10, 2023, to support an extended end-of-life for Windows 7/8/8.1

Version support policy

The latest three stable major versions are supported by the Electron team.

For example, if the latest release is 42.1.x, then the 41.0.x as well as the 40.2.x series are supported. We only support the latest minor release for each stable release series. This means that in the case of a security fix, 42.1.x will receive the fix, but we will not release a new version of 42.0.x.

The latest stable release unilaterally receives all fixes from main, and the version prior to that receives the vast majority of those fixes as time and bandwidth warrants. The oldest supported release line will receive only security fixes directly.

Chromium version support

[!TIP] Chromium's public release schedule is here.

Electron targets Chromium even-number versions, releasing every 8 weeks in concert with Chromium's 4-week release schedule. For example, Electron 26 uses Chromium 116, while Electron 27 uses Chromium 118.

Node.js version support

Electron upgrades its main branch to even-number versions of Node.js when they enter Active LTS. The schedule is as follows:

If Electron has recently updated its main branch to a new major version of Node.js, the next stable branch to be cut will be released with the new version.

Stable release lines of Electron will receive minor and patch bumps of Node.js after they are released. Patch bumps to Node.js will be released in patch releases of Electron, and minor bumps to Node.js will result in a minor release of Electron. Security-only release branches will receive security-related changes from Node.js releases, but not the full release.

Breaking API changes

When an API is changed or removed in a way that breaks existing functionality, the previous functionality will be supported for a minimum of two major versions when possible before being removed. For example, if a function takes three arguments, and that number is reduced to two in major version 10, the three-argument version would continue to work until, at minimum, major version 12. Past the minimum two-version threshold, we will attempt to support backwards compatibility beyond two versions until the maintainers feel the maintenance burden is too high to continue doing so.

[!TIP] For a canonical list of breaking changes, see the Breaking Changes document.