-
-
Notifications
You must be signed in to change notification settings - Fork 512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Friendly Notice to Update Electron (Post 2.0) #370
Comments
Should this be only during |
@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 |
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:
package.json
, recommend whenever there is a more recent patch releasepackage.json
and a new major exists that is stable, recommend upgradingThe text was updated successfully, but these errors were encountered: