Skip to content

Commit

Permalink
fix(doc): Document release steps for admins (#3063)
Browse files Browse the repository at this point in the history
  • Loading branch information
johnjbarton authored Jul 16, 2018
1 parent 93ba05a commit a701732
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions docs/dev/03-maintaining.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,18 @@ Please, make sure:
- e.g. if the first commit is `fix(web-server): serve binary files` and a second commit is “fix unit tests broken in the previous commit”, you should squash them into a single commit.
- It’s alright to ask the author of the pull request to fix any of the above.

## Releasing npm
For core collaborators with admin rights.
- Be on a good network that won't go down in the middle.
- Make sure you are sync to upstream master.
- `echo $GH_TOKEN`
- If not set, set GH_TOKEN from https://github.com/settings/tokens/new
- `npm login karmarunnerbot`
- The password is known to authorized releasers.
- `grunt release`
If the release fails, check the state of the git tags pushed to github. You may have to delete one.


## Ownership
Every project has one or more owners (or “maintainers”), listed in `owners` field of the
`package.json`. Typically, owners have push permissions.
Expand Down

0 comments on commit a701732

Please sign in to comment.