		@@ -0,1 +1,23 @@
		# Changelog

		## Release (2024-02-21)

		@ember/optional-features 2.1.0 (minor)

		#### :rocket: Enhancement
		* `@ember/optional-features`
		* [#334](https://github.com/emberjs/ember-optional-features/pull/334) Add feature for no-implicit-route-model - only effective from ember-source 5.7 ([@achambers](https://github.com/achambers))

		#### :house: Internal
		* `@ember/optional-features`
		* [#339](https://github.com/emberjs/ember-optional-features/pull/339) update release-plan ([@mansona](https://github.com/mansona))
		* [#337](https://github.com/emberjs/ember-optional-features/pull/337) Setup release plan ([@NullVoxPopuli](https://github.com/NullVoxPopuli))
		* [#338](https://github.com/emberjs/ember-optional-features/pull/338) switch to npm ([@mansona](https://github.com/mansona))
		* [#335](https://github.com/emberjs/ember-optional-features/pull/335) Test against Node 16, 18, and 20 ([@NullVoxPopuli](https://github.com/NullVoxPopuli))

		#### Committers: 3
		- Aaron Chambers ([@achambers](https://github.com/achambers))
		- Chris Manson ([@mansona](https://github.com/mansona))
		- [@NullVoxPopuli](https://github.com/NullVoxPopuli)

		## v2.0.0 (2020-08-27)
		@@ -2,0 +24,0 @@

package.json

		{
		"name": "@ember/optional-features",
		"version": "2.0.0",
		"version": "2.1.0",
		"description": "The default blueprint for ember-cli addons.",
		@@ -27,5 +27,5 @@ "keywords": [
		"dependencies": {
		"chalk": "^4.1.0",
		"ember-cli-version-checker": "^5.1.1",
		"glob": "^7.1.6",
		"chalk": "^4.1.2",
		"ember-cli-version-checker": "^5.1.2",
		"glob": "^7.1.7",
		"inquirer": "^7.3.3",
		@@ -37,13 +37,12 @@ "mkdirp": "^1.0.4",
		"broccoli-test-helper": "^2.0.0",
		"ember-cli": "~3.20.0",
		"ember-cli": "~3.23.0",
		"ember-cli-dependency-checker": "^3.2.0",
		"eslint": "^7.7.0",
		"eslint-config-prettier": "^6.11.0",
		"eslint": "^7.32.0",
		"eslint-config-prettier": "^6.15.0",
		"eslint-plugin-node": "^11.1.0",
		"eslint-plugin-prettier": "^3.1.4",
		"eslint-plugin-prettier": "^3.4.0",
		"execa": "^4.0.3",
		"prettier": "^2.1.1",
		"qunit": "^2.11.1",
		"release-it": "^13.7.0",
		"release-it-lerna-changelog": "^2.3.0"
		"prettier": "^2.3.2",
		"qunit": "^2.16.0",
		"release-plan": "^0.7.1"
		},
		@@ -55,18 +54,3 @@ "engines": {
		"registry": "https://registry.npmjs.org"
		},
		"release-it": {
		"plugins": {
		"release-it-lerna-changelog": {
		"infile": "CHANGELOG.md",
		"launchEditor": true
		}
		},
		"git": {
		"tagName": "v${version}"
		},
		"github": {
		"release": true,
		"tokenRef": "GITHUB_AUTH"
		}
		}
		}

RELEASE.md

		@@ -1,17 +0,13 @@
		# Release
		# Release Process

		Releases are mostly automated using
		[release-it](https://github.com/release-it/release-it/) and
		[lerna-changelog](https://github.com/lerna/lerna-changelog/).
		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 prepare the release once the PR is merged.


		## 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
		Since the majority of the actual release process is automated, the remaining tasks before releasing are:

		- correctly labeling all pull requests that have been merged since the last release
		- updating pull request titles so they make sense to our users

		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.
		@@ -25,39 +21,8 @@
		* documentation - Used when the PR adds or updates documentation.
		* internal - Used for internal changes that still require a mention in the
		changelog/release notes.
		* 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:

		* First, ensure that you have installed your projects dependencies:

		```
		yarn install
		```

		* Second, ensure that you have obtained a
		[GitHub personal access token][generate-token] with the `repo` scope (no
		other permissions are needed). Make sure the token is available as the
		`GITHUB_AUTH` environment variable.

		For instance:

		```bash
		export GITHUB_AUTH=abc123def456
		```

		[generate-token]: https://github.com/settings/tokens/new?scopes=repo&description=GITHUB_AUTH+env+variable

		* And last (but not least 😁) do your release.

		```
		npx release-it
		```

		[release-it](https://github.com/release-it/release-it/) manages the actual
		release process. It will prompt you to 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.
		Once the prep work is completed, the actual release is straight forward: you just need to merge the open [Plan Release](https://github.com/emberjs/ember-optional-features/pulls?q=is%3Apr+is%3Aopen+%22Prepare+Release%22+in%3Atitle) PR

.github/workflows/ci.yml

Sorry, the diff of this file is not supported yet

@ember/optional-features - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics

Worsened metrics

Dependency changes