[TASK] Prepare the 3.0.0 release (#772)

MyIntervals · Oct 1, 2019 · d68a8b5 · d68a8b5
1 parent e4a15f3
commit d68a8b5
Show file tree

Hide file tree

Showing 3 changed files with 17 additions and 5 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,6 +5,18 @@ This project adheres to [Semantic Versioning](https://semver.org/).
 
 ## x.y.z
 
+### Added
+
+### Changed
+
+### Deprecated
+
+### Removed
+
+### Fixed
+
+## 3.0.0
+
 ### Added
 - Test and document excluding entire subtree with `addExcludedSelector()`
   ([#347](https://github.com/MyIntervals/emogrifier/issues/347),

diff --git a/README.md b/README.md
@@ -461,11 +461,11 @@ They will, however, be preserved and copied to a `<style>` element in the HTML:
    changes.
 1. In the [composer.json](composer.json), update the `branch-alias` entry to
    point to the release _after_ the upcoming release.
-1. In the [README.md](README.md), update the version numbers in the section
-   [Installing with Composer](#installing-with-composer).
-1. In the [CHANGELOG.md](CHANGELOG.md), set the version number and remove any
-   empty sections.
+1. In the [CHANGELOG.md](CHANGELOG.md), create a new section with subheadings
+   for changes _after_ the upcoming release, set the version number for the
+   upcoming release, and remove any empty sections.
 1. Have the pull request reviewed and merged.
+1. Tag the new release.
 1. In the [Releases tab](https://github.com/MyIntervals/emogrifier/releases),
    create a new release and copy the change log entries to the new release.
 1. Post about the new release on social media.

diff --git a/composer.json b/composer.json
@@ -91,7 +91,7 @@
     },
     "extra": {
         "branch-alias": {
-            "dev-master": "3.0.x-dev"
+            "dev-master": "4.0.x-dev"
         }
     }
 }