Friendly Notice to Update Electron (Post 2.0)

[groundwater]

Electron 2.0 will be moving to semver according to the new Versioning Policy.

The intention is that folks should be able to use proper semver ranges, either ^2.0.0 or ~2.0.0 to admit bug fixes and/or features. I know forge currently recommends locking an exact version of electron, and we hope that will not be necessary in the future.

I would propose that, for now, forge at least recommend when someone should update electron according to the following rules:

• all rules <2.0 stay the same
• if using a pinned version >=2.0 in package.json, recommend whenever there is a more recent patch release
• if using any version range >=2.0 in package.json and a new major exists that is stable, recommend upgrading

[malept]

Should this be only during electron-forge start, or when it's packaged as well? People get irritated by warnings, if the issues I've seen are any indication.

[devlsh]

@malept I think it has to be one or the other, to avoid conflicts in API. If we use >= 2.0 at runtime, we should also do so during packaging. A few issues from people who don't have/want to spend time upgrading is more than worth being both a) on semver with Electron itself and b) being up-to-date