Skip to content

Forge 8 #4082

@erickzhao

Description

@erickzhao

This issue outlines the work for the next major version of Electron 8.

Goals

  • Bump our engines requirement to Node.js 22 and update dependencies accordingly.
  • Publish all @electron-forge/ modules as ESM-only.
  • Ensure both ESM and CJS configs are loaded properly, and that both ESM and CJS Electron apps run properly.
  • Improve native Node.js add-on support.
  • Improve documentation for public consumption.
  • Graduate all extensions to stable.
  • Deprecate/remove unused features.

Release process

The next branch is tracking work for the next major version.

Electron Forge now uses npm trusted publishing for an easier and more secure release process.

Until this issue is closed for the Electron Forge 8.0.0 release, we will be proceeding with three distinct pre-release stages, which will have their corresponding distribution tags on npm:

  • alpha: Forge 8 is not ready for general consumption, and is actively being tweaked. At this point, maintainers will be dogfooding Forge 8 in their own apps to test it out. Use at your own risk!
  • beta: Forge 8 should be stable enough for early adopters, but some breaking changes should be expected between versions.
  • rc: In preparation for an 8.0.0 release, the Release Candidate stage is considered potentially stable unless bugs occur. Maintainers will decide on when Forge is ready for a stable release.

TODO

I've created an 8.0.0 milestone of bugs and feature requests to address before the product is ready for stable.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions