Add release-it

.release-it.json

@@ -0,0 +1,16 @@
+{
+  "plugins": {
+    "release-it-lerna-changelog": {
+      "infile": "CHANGELOG.md"
+    }
+  },
+  "git": {
+    "tagName": "v${version}"
+  },
+  "npm": {
+    "publish": true
+  },
+  "github": {
+    "release": true
+  }
+}

CHANGELOG.md

@@ -1,4 +1,11 @@
-# Changelog
+## v6.7.2 (2019-11-03)
+
+#### :bug: Bug Fix
+* [#372](https://github.com/ember-cli/ember-fetch/pull/372) fix: throwing w/ fresh ember-cli-fastboot serve ([@xg-wang]
+g-wang))
+
+#### Committers: 1
+- Thomas Wang ([@xg-wang](https://github.com/xg-wang)) 
 
 ## v6.7.1 (2019-09-12)
 

RELEASE.md

@@ -0,0 +1,42 @@
+# Release
+
+Releases are mostly automated using
+[release-it](https://github.com/release-it/release-it/) and
+[lerna-changelog](https://github.com/lerna/lerna-changelog/).
+
+
+## Preparation
+
+Since the majority of the actual release process is automated, the primary
+remaining task prior to releasing is confirming that all pull requests that
+have been merged since the last release have been labeled with the appropriate
+`lerna-changelog` labels and the titles have been updated to ensure they
+represent something that would make sense to our users. Some great information
+on why this is important can be found at
+[keepachangelog.com](https://keepachangelog.com/en/1.0.0/), but the overall
+guiding principles here is that changelogs are for humans, not machines.
+
+When reviewing merged PR's the labels to be used are:
+
+* breaking - Used when the PR is considered a breaking change.
+* enhancement - Used when the PR adds a new feature or enhancement.
+* bug - Used when the PR fixes a bug included in a previous release.
+* documentation - Used when the PR adds or updates documentation.
+* internal - Used for internal changes that still require a mention in the
+  changelog/release notes.
+
+
+## Release
+
+Once the prep work is completed, the actual release is straight forward:
+
+```
+yarn install
+yarn release
+```
+
+The `release` script leverages
+[release-it](https://github.com/release-it/release-it/) to do the mechanical
+release process. It will prompt you through the process of choosing the version
+number, tagging, pushing the tag and commits, etc.
+

package.json

@@ -1,6 +1,6 @@
 {
   "name": "ember-fetch",
-  "version": "6.7.1",
+  "version": "6.7.2",
   "description": "HTML5 Fetch polyfill (as an ember-addon)",
   "typings": "./index.d.ts",
   "keywords": [
@@ -15,6 +15,7 @@
   "scripts": {
     "build": "ember build",
     "changelog": "lerna-changelog",
+    "release": "release-it",
     "lint:js": "eslint . --cache",
     "start": "ember serve",
     "test": "ember test",
@@ -64,7 +65,6 @@
     "ember-cli-inject-live-reload": "^2.0.1",
     "ember-cli-pretender": "^3.2.0",
     "ember-cli-qunit": "^4.3.2",
-    "ember-cli-release": "^0.2.9",
     "ember-cli-typescript-blueprints": "^2.0.0",
     "ember-cli-uglify": "^3.0.0",
     "ember-data": "~3.14.0",
@@ -83,6 +83,8 @@
     "lerna-changelog": "^0.8.3",
     "loader.js": "^4.2.3",
     "mocha": "^6.1.4",
+    "release-it": "^12.4.3",
+    "release-it-lerna-changelog": "^1.0.3",
     "typescript": "^3.7.2"
   },
   "resolutions": {