Skip to content

Commit

Permalink
Update release setup. (#1302)
Browse files Browse the repository at this point in the history
The result of running `npx create-rwjblue-release-it-setup --update`.

This will prevent an issue that you will run into if you attempt to
publish a new version while your `release-it` version is 14.2.0 and your
`release-it-lerna-changelog` version is 2.4.0.
  • Loading branch information
rwjblue committed Oct 21, 2020
1 parent c35a790 commit 7015ac2
Show file tree
Hide file tree
Showing 3 changed files with 56 additions and 202 deletions.
39 changes: 16 additions & 23 deletions RELEASE.md
@@ -1,10 +1,9 @@
# 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/).


## Preparation

Since the majority of the actual release process is automated, the primary
Expand All @@ -25,39 +24,33 @@ When reviewing merged PR's the labels to be used are:
* 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 `release-it` installed globally, generally done by
using one of the following commands:
* First, ensure that you have installed your projects dependencies:

```sh
yarn install
```
# using https://volta.sh
volta install release-it

# using Yarn
yarn global add release-it
* 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.

# using npm
npm install --global release-it
```
For instance:

* Second, ensure that you have installed your projects dependencies:
```bash
export GITHUB_AUTH=abc123def456
```

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

* 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.
* And last (but not least 😁) do your release.

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

[release-it](https://github.com/release-it/release-it/) manages the actual
Expand Down
18 changes: 9 additions & 9 deletions package.json
Expand Up @@ -34,6 +34,14 @@
"test:ember": "ember test",
"test:ember-compatibility": "ember try:each"
},
"husky": {
"hooks": {
"pre-commit": "lint-staged"
}
},
"lint-staged": {
"*.js": "eslint --cache --fix"
},
"resolutions": {
"ember-cli-htmlbars/semver": "~7.0.0",
"ember-concurrency": "^1.3.0",
Expand Down Expand Up @@ -130,7 +138,7 @@
"prettier": "^2.1.2",
"qunit-dom": "^1.5.0",
"release-it": "^14.2.0",
"release-it-lerna-changelog": "^2.4.0",
"release-it-lerna-changelog": "^3.0.0",
"striptags": "^3.0.0"
},
"engines": {
Expand Down Expand Up @@ -172,13 +180,5 @@
"release": true,
"tokenRef": "GITHUB_AUTH"
}
},
"husky": {
"hooks": {
"pre-commit": "lint-staged"
}
},
"lint-staged": {
"*.js": "eslint --cache --fix"
}
}

0 comments on commit 7015ac2

Please sign in to comment.