Versiones de Electrón
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.
Línea de tiempo
| Electron | Alfa | Beta | Estable | EOL | Chrome | Nodo | Supported |
|---|---|---|---|---|---|---|---|
| 31.0.0 | 2024-Apr-18 | 2024-May-15 | 2024-Jun-11 | 2025-Jan-07 | M126 | TBD | ✅ |
| 30.0.0 | 2024-fe-22 | 2024-Mar-20 | 2024-Apr-16 | 2024-Oct-15 | M124 | v20.11 | ✅ |
| 29.0.0 | 2023-Dec-07 | 2024-Jan-24 | 2024-fe-20 | 2024-Ago-20 | M122 | v20.9 | ✅ |
| 28.0.0 | 2023-Oct-11 | 2023-nov-06 | 2023-Dec-05 | 2024-Jun-11 | M120 | v18.18 | ✅ |
| 27.0.0 | 2023-Ago-17 | 2023-Sep-13 | 2023-Oct-10 | 2024-Apr-16 | M118 | v18.17 | 🚫 |
| 26.0.0 | 2023-Jun-01 | 2023-Jun-27 | 2023-Ago-15 | 2024-fe-20 | M116 | v18.16 | 🚫 |
| 25.0.0 | 2023-Apr-10 | 2023-May-02 | 2023-May-30 | 2023-Dec-05 | M114 | v18.15 | 🚫 |
| 24.0.0 | 2023-fe-09 | 2023-Mar-07 | 2023-Apr-04 | 2023-Oct-10 | M112 | v18.14 | 🚫 |
| 23.0.0 | 2022-Dec-01 | 2023-Jan-10 | 2023-fe-07 | 2023-Ago-15 | M110 | v18.12 | 🚫 |
| 22.0.0 | 2022-Sep-29 | 2022-Oct-25 | 2022-nov-29 | 2023-Oct-10 | M108 | v16.17 | 🚫 |
| 21.0.0 | 2022-Ago-04 | 2022-Ago-30 | 2022-Sep-27 | 2023-Apr-04 | M106 | v16.16 | 🚫 |
| 20.0.0 | 2022-May-26 | 2022-Jun-21 | 2022-Ago-02 | 2023-fe-07 | M104 | v16.15 | 🚫 |
| 19.0.0 | 2022-Mar-31 | 2022-Apr-26 | 2022-May-24 | 2022-nov-29 | M102 | v16.14 | 🚫 |
| 18.0.0 | 2022-fe-03 | 2022-Mar-03 | 2022-Mar-29 | 2022-Sep-27 | M100 | v16.13 | 🚫 |
| 17.0.0 | 2021-nov-18 | 2022-Jan-06 | 2022-fe-01 | 2022-Ago-02 | M98 | v16.13 | 🚫 |
| 16.0.0 | 23-Sept-2021 | 2021-Oct-20 | 2021-nov-16 | 2022-May-24 | M96 | v16.9 | 🚫 |
| 15.0.0 | 2021-Jul-20 | 01-Sept-2021 | 21-Sept-2021 | 2022-May-24 | M94 | v16.5 | 🚫 |
| 14.0.0 | -- | 2021-May-27 | 2021-Ago-31 | 2022-Mar-29 | M93 | v14.17 | 🚫 |
| 13.0.0 | -- | 2021-Mar-04 | 2021-May-25 | 2022-fe-01 | M91 | v14.16 | 🚫 |
| 12.0.0 | -- | 2020-nov-19 | 2021-Mar-02 | 2021-nov-16 | M89 | v14.16 | 🚫 |
| 11.0.0 | -- | 2020-Ago-27 | 2020-nov-17 | 2021-Ago-31 | M87 | v12.18 | 🚫 |
| 10.0.0 | -- | 2020-May-21 | 2020-Ago-25 | 2021-May-25 | M85 | v12.16 | 🚫 |
| 9.0.0 | -- | 2020-fe-06 | 2020-May-19 | 2021-Mar-02 | M83 | v12.14 | 🚫 |
| 8.0.0 | -- | 2019-Oct-24 | 2020-fe-04 | 2020-nov-17 | M80 | v12.13 | 🚫 |
| 7.0.0 | -- | 2019-Ago-01 | 2019-Oct-22 | 2020-Ago-25 | M78 | v12.8 | 🚫 |
| 6.0.0 | -- | 2019-Apr-25 | 2019-Jul-30 | 2020-May-19 | M76 | v12.14.0 | 🚫 |
| 5.0.0 | -- | 2019-Jan-22 | 2019-Apr-23 | 2020-fe-04 | M73 | v12.0 | 🚫 |
| 4.0.0 | -- | 2018-Oct-11 | 2018-Dec-20 | 2019-Oct-22 | M69 | v10.11 | 🚫 |
| 3.0.0 | -- | 2018-Jun-21 | 2018-Sep-18 | 2019-Jul-30 | M66 | v10.2 | 🚫 |
| 2.0.0 | -- | 2018-fe-21 | 2018-May-01 | 2019-Apr-23 | M61 | v8.9 | 🚫 |
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.
Notas:
- The
-alpha.1,-beta.1, andstabledates are our solid release dates. - We strive for weekly alpha/beta releases, but we often release more than scheduled.
- Todas las fechas son nuestras metas pero puede haber razones para ajustar el plazo de la versión estable, tales como errores de seguridad.
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
Las últimas tres versiones stable son soportadas por el equipo Electron. Por ejemplo, si la última versión es 6.1.x, entonces la 5.0.x así como la series 4.2.x son soportadas. Solo soportamos la última versión minor por cada versión estable. 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.
La última versión estable recibe unilateralmente todas las correcciones de main, y la versión anterior recibe la gran mayoría de esas correcciones como el tiempo y el ancho de banda lo permite. Las versiones más antiguas soportadas solamente van a recibir correcciones de seguridad directamente.
Chromium version support
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:
As a rule, stable branches of Electron do not receive Node.js upgrades after they have been cut. 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.
Patch upgrades of Node that contain significant security or bug fixes, and are submitted more than 2 weeks prior to a stable release date, will be accepted into an Electron alpha or beta release branch.
Minor upgrades of Node that contain significant security or bug fixes, and are submitted more than 2 weeks prior to a stable release date may be accepted into an Electron alpha or beta release branch on a case-by-case basis. These requests will be reviewed and voted on by the Releases Working Group, to ensure minimal disruption for developers who may be consuming alpha or beta releases.
Breaking API changes
Cuando una API es cambiada o eliminada de alguna manera eso rompe la funcionalidad existente, la funcionalidad anterior será mantenida por mínimo dos versiones principales cuando sea posible antes de eliminarla. 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.
Fin de vida
Cuando una rama de lanzamiento llega al final de su ciclo de soporte, la serie quedará obsoleta en NPM y se realizará una versión final de fin de soporte. Este lanzamiento agregará una advertencia para informar que una versión no soportada de Electron está en uso.
Estos pasos son para ayudar a los desarrolladores de aplicaciones a saber cuándo una rama que están utilizando no recibe soporte, pero sin ser excesivamente intrusiva para los usuarios finales.
Si una aplicación tiene circunstancias excepcionales y necesita permanecer en una serie de Electron no admitida, los desarrolladores pueden silenciar la advertencia de fin de soporte al omitir la versión final de package.json devDependencies de la aplicación. Por ejemplo, dado que la serie 1-6-x finalizó con una versión 1.6.18 de fin de soporte, los desarrolladores podrían optar por permanecer en la serie 1-6-x sin advertencias con un devDependency de "electron": 1.6.0 - 1.6.17.