Skip to content

Commit 90c8139

Browse files
author
Robert Jackson
committed
Update automated release settings.
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.
1 parent f142698 commit 90c8139

File tree

3 files changed

+373
-675
lines changed

3 files changed

+373
-675
lines changed

RELEASE.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ have been merged since the last release have been labeled with the appropriate
1414
represent something that would make sense to our users. Some great information
1515
on why this is important can be found at
1616
[keepachangelog.com](https://keepachangelog.com/en/1.0.0/), but the overall
17-
guiding principles here is that changelogs are for humans, not machines.
17+
guiding principle here is that changelogs are for humans, not machines.
1818

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

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

4949
```
50-
# using yarn
5150
yarn install
52-
53-
# using npm
54-
npm install
5551
```
5652

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

5958
```
59+
export GITHUB_AUTH="f941e0..."
6060
release-it
6161
```
6262

6363
[release-it](https://github.com/release-it/release-it/) manages the actual
64-
release process. It will prompt you through the process of choosing the version
65-
number, tagging, pushing the tag and commits, etc.
64+
release process. It will prompt you to to choose the version number after which
65+
you will have the chance to hand tweak the changelog to be used (for the
66+
`CHANGELOG.md` and GitHub release), then `release-it` continues on to tagging,
67+
pushing the tag and commits, etc.

package.json

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,6 @@
2222
},
2323
"scripts": {
2424
"build": "ember build",
25-
"changelog": "lerna-changelog",
2625
"lint:js": "eslint .",
2726
"start": "ember serve",
2827
"test": "ember test",
@@ -54,11 +53,10 @@
5453
"eslint": "^6.8.0",
5554
"eslint-plugin-ember": "^7.8.1",
5655
"eslint-plugin-node": "^10.0.0",
57-
"lerna-changelog": "^0.8.3",
5856
"loader.js": "^4.7.0",
5957
"qunit-dom": "^0.9.0",
6058
"release-it": "^13.5.2",
61-
"release-it-lerna-changelog": "^1.0.3"
59+
"release-it-lerna-changelog": "^2.1.2"
6260
},
6361
"engines": {
6462
"node": ">= 10.*"
@@ -72,14 +70,16 @@
7270
"release-it": {
7371
"plugins": {
7472
"release-it-lerna-changelog": {
75-
"infile": "CHANGELOG.md"
73+
"infile": "CHANGELOG.md",
74+
"launchEditor": true
7675
}
7776
},
7877
"git": {
7978
"tagName": "v${version}"
8079
},
8180
"github": {
82-
"release": true
81+
"release": true,
82+
"tokenRef": "GITHUB_AUTH"
8383
}
8484
}
8585
}

0 commit comments

Comments
 (0)