Aller au contenu principal

Versions d'Electron

Electron frequently releases major versions alongside every other Chromium release. This document focuses on the release cadence and version support policy. For a more in-depth guide on our git branches and how Electron uses semantic versions, check out our Electron Versioning doc.

Timeline

ElectronAlphaBetaStableChromeNodeSupported
2.0.0--2018-Feb-212018-May-01M61v8.9🚫
3.0.0--2018-Jun-2118-Sept-2018M66v10.2🚫
4.0.0--11-Oct-20182018-Dec-20M69v10.11🚫
5.0.0--22-Janv-20192019-Apr-24M73v12.0🚫
6.0.0--2019-May-012019-Jul-30M76v12.4🚫
7.0.0--2019-Aug-0122-Oct-2019M78v12.8🚫
8.0.0--24-Oct-20192020-Feb-04M80v12.13🚫
9.0.0--2020-Feb-062020-May-19M83v12.14🚫
10.0.0--2020-May-212020-Aug-25M85v12.16🚫
11.0.0--2020-Aug-2717-Nov-2020M87v12.18🚫
12.0.0--19-Nov-20202021-Mar-02M89v14.16🚫
13.0.0--2021-Mar-042021-May-25M91v14.16🚫
14.0.0--2021-May-272021-Aug-31M93v14.17🚫
15.0.02021-Jul-2001-Sept-202121-Sept-2021M94v16.5🚫
16.0.023-Sept-202120-Oct-202116-Nov-2021M96v16.9🚫
17.0.018-Nov-202106-Janv-20222022-Feb-01M98v16.13
18.0.02022-Feb-032022-Mar-032022-Mar-29M100v16.13
19.0.02022-Mar-312022-Apr-262022-May-24M102v16.14
20.0.02022-May-262022-Jun-212022-Aug-02M104TBD

Remarque :

  • 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.
  • Toutes les dates sont nos objectifs, mais il peut y avoir des raisons d’ajuster la date limite, telles que des problèmes de sécurité.

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).
Chrome release dates

Chromium has the own public release schedule here.

Version support policy

info

Beginning in September 2021 (Electron 15), the Electron team will temporarily support the latest four stable major versions. This extended support is intended to help Electron developers transition to the new 8-week release cadence, and will continue until the release of Electron 19. At that time, the Electron team will drop support back to the latest three stable major versions.

Les trois dernières versions majeures stables sont prises en charge par l'équipe Electron. For example, if the latest release is 6.1.x, then the 5.0.x as well as the 4.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, 6.1.x will receive the fix, but we will not release a new version of 6.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.

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.

End-of-life

Quand une branche de version arrive au terme de son cycle de support, les révisions associées sont rendues obsolètes dans NPM et une toute dernière révision de fin de support est mise à disposition. Cette révision signalera alors que la version d'Electron utilisée n'est plus supportée.

Ces étapes permettent aux développeurs d'applications d'être informés que la branche qu'ils utilisent ne sera bientôt plus supportée, sans toutefois trop importuner l'utilisateur final.

Si, pour une raison exceptionnelle, une application nécessite de rester sur une version d'Electron qui n'est plus supportée, les développeurs peuvent désactiver l'avertissement de fin de support en omettant d'ajouter dans la collection devDependencies du fichier package.json la dernière révision de fin de support. Par exemple, comme la version 1.6 est clôturée par la révision de fin de support 1.6.18, les développeurs pourraient choisir de continuer à l'utiliser sans message d'avertissement en précisant, dans devDependency, "electron": 1.6.0 - 1.6.17.