Skip to content

Commit

Permalink
update
Browse files Browse the repository at this point in the history
  • Loading branch information
mtrezza committed May 2, 2021
1 parent 6224efd commit 36bb09e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -290,7 +290,7 @@ Parse Server follows [semantic versioning](https://semver.org) with a flavor of

Syntax: `[major]`**.**`[minor]`**.**`[patch]`**-**`[pre-release-label]`

- The `major` version increments every year and may include changes that are *not* backwards compatible.
- The `major` version increments with the first release of every year and may include changes that are *not* backwards compatible.
- The `minor` version increments during the year and may include new features or improvements of existing features that are backwards compatible.
- The `patch` version increments during the year and may include bug fixes that are backwards compatible.
- The `pre-release-label` is optional for pre-release versions such as:
Expand All @@ -299,7 +299,7 @@ Syntax: `[major]`**.**`[minor]`**.**`[patch]`**-**`[pre-release-label]`
- `-rc0` (unlikely to contain bugs, no change in features until release)

Exceptions:
- The `major` version may increment during the year in the unlikely event that a breaking change is so urgent that it cannot wait for the next yearly release. This should be as rare as the planetary alignment of Jupiter and Saturn.
- The `major` version may increment during the year in the unlikely event that a breaking change is so urgent that it cannot wait for the next yearly release. An example would be a vulnerability fix that leads to an unavoidable breaking change.
- Bug fixes of security vulnerabilities are `patch` releases, unless they cause a breaking change, then they are `major` releases.

## Code of Conduct
Expand Down

0 comments on commit 36bb09e

Please sign in to comment.