What’s important about the second point is that apps using ^ should still be able to expect a reasonable level of stability. Use ^2.0.0 to admit non-breaking reasonably stable feature work as well as security and bug fixes.Use ~2.0.0 to admit only stability or security related fixes to your 2.0.0 release.Our goal is to allow the following standard semver ranges in package.json : At the same time, locking to a fixed version is dangerous because you’re ignoring security patches and bug fixes that may have come out since your version. Even seemingly innocent features can introduce regressions in complex applications. Beta releases and bug fixes ĭevelopers want to know which releases are safe to use. We discourage this, but recognize that it makes life easier for many app developers. Older lines will not be supported by the Electron project, but other groups can take ownership and backport stability and security fixes on their own. For more details on which versions are supported, see our Electron Releases doc. We allow for multiple stabilization branches to exist simultaneously, one for each supported version.

Prior to that we used minor version lines and named them as $MAJOR-$MINOR-x e.g. Since Electron 8, stabilization branches are always major version lines, and named against the following template $MAJOR-x-y e.g. These branches are never merged back to main. Stabilization branches are branches that run parallel to main, taking in only cherry-picked commits that are related to security or stability. Fixes that can be backported will likely be cherry-picked as patches. Note that most Chromium updates will be considered breaking. Major Version Incrementsįor more information, see the Semantic Versioning 2.0.0 spec. SemVer īelow is a table explicitly mapping types of changes to their corresponding category of SemVer (e.g. We will cover in detail how git branching works, how npm tagging works, what developers should expect to see, and how one can backport changes. The main branch is versionless only stabilization branches contain version information.Introduction of conventional commit messages.Introduction of semver-compliant -beta tags.Each change is intended to satisfy the needs and priorities of developers/maintainers and app developers. There are several major changes from our 1.x strategy outlined below.

Electron 26.2.1 for mac download