npx create-release-plan-setup@latest --update

Author: NullVoxPopuli

CHANGELOG.md

@@ -1,3 +1,5 @@
+# Changelog
+
 
 
 

RELEASE.md

@@ -1,11 +1,27 @@
-# Release Instructions
+# Release Process
 
-1. Check that notable PRs since the last release are labeled and have clear and consistent titles
+Releases in this repo are mostly automated using [release-plan](https://github.com/embroider-build/release-plan/). Once you label all your PRs correctly (see below) you will have an automatically generated PR that updates your CHANGELOG.md file and a `.release-plan.json` that is used to prepare the release once the PR is merged.
 
-2. `git pull` the latest master and ensure that `git status` shows no local changes
+## Preparation
 
-3. `export GITHUB_AUTH="..."` with a [GitHub access token](https://github.com/settings/tokens/new?scopes=repo&description=release-it) with "repo" access so [release-it](https://github.com/release-it/release-it) can conduct a GitHub release and [lerna-changelog](https://github.com/lerna/lerna-changelog) can download the change history
+Since the majority of the actual release process is automated, the remaining tasks before releasing are: 
 
-4. `export EDITOR="vim"` to choose an editor for editing the changelog
+-  correctly labeling **all** pull requests that have been merged since the last release
+-  updating pull request titles so they make sense to our users
 
-5. `pnpm release` (uses [@release-it-plugins/lerna-changelog](https://github.com/release-it-plugins/lerna-changelog) to handle versioning, the changelog, publishing to GitHub and NPM, etc)
+Some great information on why this is important can be found at [keepachangelog.com](https://keepachangelog.com/en/1.1.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 - Internal changes or things that don't fit in any other category.
+
+**Note:** `release-plan` requires that **all** PRs are labeled. If a PR doesn't fit in a category it's fine to label it as `internal`
+
+## Release
+
+Once the prep work is completed, the actual release is straight forward: you just need to merge the open [Plan Release](https://github.com/ember-cli/eslint-plugin-ember/pulls?q=is%3Apr+is%3Aopen+%22Prepare+Release%22+in%3Atitle) PR

package.json

@@ -101,6 +101,7 @@
     "npm-run-all": "^4.1.5",
     "prettier": "^3.0.3",
     "release-it": "^17.0.0",
+    "release-plan": "^0.9.0",
     "sort-package-json": "^2.6.0",
     "typescript": "^5.2.2",
     "typescript-eslint": "^8.7.0",