Add release-it setup

Author: Turbo87

.release-it.js

@@ -0,0 +1,20 @@
+module.exports = {
+  plugins: {
+    '@release-it-plugins/lerna-changelog': {
+      infile: 'CHANGELOG.md',
+      launchEditor: true,
+    },
+  },
+  git: {
+    commitMessage: 'v${version}',
+    tagName: 'v${version}',
+  },
+  github: {
+    release: true,
+    releaseName: 'v${version}',
+    tokenRef: 'GITHUB_AUTH',
+  },
+  npm: {
+    publish: false,
+  },
+};

RELEASE.md

@@ -0,0 +1,56 @@
+# 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 principle 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:
+
+* First, ensure that you have an environment variable with your GitHub token
+  setup as `GITHUB_AUTH`. This token will be used for generating your changelog
+  (unauthenticated requests to the GitHub API are heavily throttled) and for
+  creating the GitHub release. Only "repo" access is needed; no "admin"
+  or other scopes are required.
+
+* Next, ensure that you have installed your projects dependencies:
+
+```
+pnpm install
+```
+
+* And last (but not least 😁) do your release:
+
+```
+pnpm release
+```
+
+[release-it](https://github.com/release-it/release-it/) manages the actual
+release process. It will prompt you to choose the version number after which
+you will have the chance to hand tweak the changelog to be used (for the
+`CHANGELOG.md` and GitHub release), then `release-it` continues on to tagging,
+pushing the tag and commits, etc. Finally, GitHub Actions will build the commit
+and push the release to npm.

package.json

@@ -20,6 +20,7 @@
     "lint:hbs:fix": "ember-template-lint . --fix",
     "lint:js": "eslint . --cache",
     "lint:js:fix": "eslint . --fix",
+    "release": "release-it",
     "start": "ember serve",
     "test": "ember test"
   },
@@ -33,6 +34,7 @@
     "@embroider/test-setup": "1.8.3",
     "@glimmer/component": "1.1.2",
     "@glimmer/tracking": "1.1.2",
+    "@release-it-plugins/lerna-changelog": "5.0.0",
     "babel-eslint": "10.1.0",
     "broccoli-asset-rev": "3.0.0",
     "ember-auto-import": "2.4.3",
@@ -63,6 +65,7 @@
     "prettier": "2.7.1",
     "qunit": "2.19.3",
     "qunit-dom": "2.0.0",
+    "release-it": "15.5.0",
     "webpack": "5.74.0"
   },
   "engines": {