|
2 | 2 |
|
3 | 3 | If you've been using Node and npm for a while, you are probably aware of [Semantic Versioning], or SemVer for short. It's a convention for specifying version numbers for software that helps communicate intentions to the users of your software. |
4 | 4 |
|
5 | | -## Overview of Semantic Versioning |
6 | | - |
7 | | -Semantic versions are always made up of (at least) three numbers: |
8 | | - |
9 | | -``` |
10 | | -major.minor.patch |
11 | | -``` |
12 | | - |
13 | | -Semantic version numbers are bumped (incremented) using the following rules: |
14 | | - |
15 | | -* **Major** is for changes that break backwards compatibility. |
16 | | -* **Minor** is for new features that don't break backwards compatibility. |
17 | | -* **Patch** is for bug fixes and other minor changes. |
18 | | - |
19 | | -A simple mnemonic for remembering this scheme is as follows: |
20 | | - |
21 | | -``` |
22 | | -breaking.feature.fix |
23 | | -``` |
24 | | - |
25 | | -Unstable versions may also have a _pre-release identifier_. See |
26 | | -[Prereleases](#prereleases). |
27 | | - |
28 | | -## Electron Versioning |
29 | | - |
30 | 5 | Due to its dependency on Node and Chromium, it is not possible for the Electron |
31 | | -project to adhere to a strict SemVer policy. **You should therefore always |
32 | | -reference a specific version of Electron.** |
| 6 | +project to adhere to a strict [Semantic Versioning] policy. **You should |
| 7 | +therefore always reference a specific version of Electron.** |
33 | 8 |
|
34 | 9 | Electron version numbers are bumped using the following rules: |
35 | 10 |
|
@@ -75,4 +50,4 @@ The `latest` and `next` [npm dist tags] are also used: |
75 | 50 | [Semantic Versioning]: http://semver.org |
76 | 51 | [pre-release identifier]: http://semver.org/#spec-item-9 |
77 | 52 | [npm dist tags]: https://docs.npmjs.com/cli/dist-tag |
78 | | -[normal version]: http://semver.org/#spec-item-2 |
| 53 | +[normal version]: http://semver.org/#spec-item-2 |
0 commit comments