Skip to content

Commit

Permalink
Update automated release settings.
Browse files Browse the repository at this point in the history
This is the result of running `npx create-rwjblue-release-it-setup --update`.

The main changes are:

* Allow easier review before publishing (launchEditor)
* Remove older / unused `lerna-changelog` dep (this comes from
  release-it-lerna-changelog now)
* Fix some typos in RELEASE.md.
  • Loading branch information
rwjblue committed Apr 11, 2020
1 parent f142698 commit 90c8139
Show file tree
Hide file tree
Showing 3 changed files with 373 additions and 675 deletions.
18 changes: 10 additions & 8 deletions RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ have been merged since the last release have been labeled with the appropriate
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.
guiding principle here is that changelogs are for humans, not machines.

When reviewing merged PR's the labels to be used are:

Expand Down Expand Up @@ -47,19 +47,21 @@ npm install --global release-it
* Second, ensure that you have installed your projects dependencies:

```
# using yarn
yarn install
# using npm
npm install
```

* And last (but not least 😁) do your release:
* And last (but not least 😁) do your release. It requires a
[GitHub personal access token](https://github.com/settings/tokens) as
`$GITHUB_AUTH` environment variable. Only "repo" access is needed; no "admin"
or other scopes are required.

```
export GITHUB_AUTH="f941e0..."
release-it
```

[release-it](https://github.com/release-it/release-it/) manages the actual
release process. It will prompt you through the process of choosing the version
number, tagging, pushing the tag and commits, etc.
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.
10 changes: 5 additions & 5 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,6 @@
},
"scripts": {
"build": "ember build",
"changelog": "lerna-changelog",
"lint:js": "eslint .",
"start": "ember serve",
"test": "ember test",
Expand Down Expand Up @@ -54,11 +53,10 @@
"eslint": "^6.8.0",
"eslint-plugin-ember": "^7.8.1",
"eslint-plugin-node": "^10.0.0",
"lerna-changelog": "^0.8.3",
"loader.js": "^4.7.0",
"qunit-dom": "^0.9.0",
"release-it": "^13.5.2",
"release-it-lerna-changelog": "^1.0.3"
"release-it-lerna-changelog": "^2.1.2"
},
"engines": {
"node": ">= 10.*"
Expand All @@ -72,14 +70,16 @@
"release-it": {
"plugins": {
"release-it-lerna-changelog": {
"infile": "CHANGELOG.md"
"infile": "CHANGELOG.md",
"launchEditor": true
}
},
"git": {
"tagName": "v${version}"
},
"github": {
"release": true
"release": true,
"tokenRef": "GITHUB_AUTH"
}
}
}
Loading

0 comments on commit 90c8139

Please sign in to comment.