diff options
author | Kirill Chibisov <contact@kchibisov.com> | 2020-03-30 20:22:01 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-03-30 17:22:01 +0000 |
commit | 13eb50de799c4c6f7ebed1a7fa1ab25b378580bb (patch) | |
tree | bdc42357285a7b9e003a23135915a71b950c0f8b | |
parent | f80e8eca73a16f450c66902fe66982fb228654fb (diff) |
Remove 0.4.2 changelog suffix
-rw-r--r-- | CHANGELOG.md | 2 | ||||
-rw-r--r-- | CONTRIBUTING.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index e5145b64..a71e218b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -24,7 +24,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Fixed - Tabstops not being reset with `reset` -## 0.4.2-dev +## 0.4.2 ### Packaging diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1ffb8802..961be9e1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -113,7 +113,6 @@ The exact steps for an exemplary `1.2.3` release might look like this: 1. Initially, the version on the latest master is `1.2.3-dev` 2. A new `v1.2.3` branch is created for the release 3. On master, the version is bumped to `1.2.4-dev` - and the `-dev` is stripped from previous change log entries 4. In the branch, the version is bumped to `1.2.3-rc1` 5. The new commit in the branch is tagged as `v1.2.3-rc1` 6. A GitHub release is created for the `v1.2.3-rc1` tag @@ -126,6 +125,7 @@ The exact steps for an exemplary `1.2.3` release might look like this: 11. A GitHub release is created for the `v1.2.3` tag 12. The changelog since the last stable release (**not** RC) is added to the GitHub release description + 13. The `-dev` is stripped from previous changelog entries # Contact |