Versiones de Electrón | Electron Saltar al contenido principal Electron Documentación API Blog Herramientas * Electron Forge * Electron Fiddle Comunidad * Gobernanza * Muestra * Recursos Lanzamientos Español * English * Deutsch * Español * Français * 日本語 * Português * Русский * 中文 Búsqueda * Empezar * Procesos en Electron * Mejores Prácticas * Ejemplos * Desarrollo * Native Node Modules * Distribución * Pruebas y depuración * Referencias * Restaurar archivos borrados * Versiones de Electrón * Versionado de Electron * Preguntas más frecuentes sobre Electron * Glosario * Contribuyentes * * Referencias * Versiones de Electrón En esta página 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. [!TIP] See the Electron Versioning document for more details on how Electron is versioned. Línea de tiempo ​ 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. Notas: * 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. * 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 42.1.x, entonces la 41.0.x así como la series 40.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, 42.1.x will receive the fix, but we will not release a new version of 42.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 ​ [!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 ​ 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. [!TIP] For a canonical list of breaking changes, see the Breaking Changes document. Editar esta página Anterior Restaurar archivos borrados Siguiente Versionado de Electron * Línea de tiempo * Version support policy * Chromium version support * Node.js version support * Breaking API changes Documentación * Empezar * Referencia de la API Listas de verificación * Rendimiento * Seguridad Herramientas * Electron Forge * Electron Fiddle Comunidad * Gobernanza * Recursos * Discord * Bluesky * X * Mastodon * Stack Overflow Más * GitHub * Open Collective * Infraestructura de Pizarra Hosting and infrastructure graciously provided by