• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.

I'd like to have a solid plan for getting v6 out the door.

TODO

In no particular order.

• Simple import from v5 config in package.json to v6 config (Add simple Importer from Forge 5.x to 6.x #653)
• Another pass on the documentation (including actually having a front page)
• Migrate electronforge.io to actually using the v6 docs
• Move https://github.com/MarshallOfSound/electron-forge-docs to the electron-forge org (will this break gitbook?)
  • Update tools/sync-readmes.ts when this happens
  • Fix gitbook sync
• Update templates (Update to Electron Forge v6 with a Webpack template electron-userland/electron-forge-templates#64)
  • Add at least one template with webpack
• Last upgrade of as many dependencies as possible
  • Upgrade to Electron Packager 14, when it's released
  • Upgrade to @malept/electron-installer-flatpak 0.10.0, when it's released
  • Upgrade to electron-installer-snap 4, when it's released
  • Upgrade to electron-winstaller 4, when it's released
• Replace s3 due to [s3] publish fails with "callback called twice" #479 Unfortunately not necessary for the release
• Try to resolve any pending PRs
• Figure out what to do with the electron-forge NPM package
• Add docs to CONTRIBUTING.md on how to develop on Electron Forge (e.g., install bolt globally)
• Make sure packages like create-electron-app are updated appropriately
• Assist downstream packages like ember-electron with upgrading (this will probably happen post-release)
• Native modules in webpack When using the webpack plugin, unable to find native modules #703
• [v6] webpack: keytar native module has hardcoded path #1029 (bug with webpack + certain native modules)
• Add note mentioning the experimental nature of native modules + webpack