Skip to content

Commit

Permalink
chore: run linter before release task
Browse files Browse the repository at this point in the history
  • Loading branch information
fforbeck committed Aug 11, 2021
1 parent 3c76d10 commit 3e20f8b
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 8 deletions.
13 changes: 6 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -192,20 +192,19 @@ Then execute the following script:

> npm run verify rinkeby
### Release
### Release

1. Checkout `master` and pull the latest
2. Locally run `npm run release`
3. Choose a new semver version number
4. **In the background the following will now happen**:
1. the `package.json` version will be bumped
2. a new Git tag created
3. version bump and tag pushed to `master`
4. GitHub Release page will open, set the release name, edit the changelog if needed, and publish
5. `publish.yaml` will execute (due to the new release tag) to publish the new package version to the NPM registry.
1. the `package.json` version will be bumped
2. a new Git tag created
3. version bump and tag pushed to `master`
4. GitHub Release page will open, set the release name, edit the changelog if needed, and publish
5. `publish.yaml` will execute (due to the new release tag) to publish the new package version to the NPM registry.
5. Done!


## Contribute

Tribute exists thanks to its contributors. There are many ways you can participate and help build high quality software. Check out the [contribution guide](CONTRIBUTING.md)!
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@
"migrate": "truffle migrate --network",
"test": "mocha --timeout 2000000 --exit --recursive",
"verify": "scripts/verify.js",
"release": "np --no-publish --no-yarn"
"release": "npm run lint:fix && np --no-publish --no-yarn"
},
"repository": {
"type": "git",
Expand Down

0 comments on commit 3e20f8b

Please sign in to comment.