Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(releasing): Document release steps for admins #3063

Merged
merged 1 commit into from
Jul 16, 2018
Merged

docs(releasing): Document release steps for admins #3063

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/dev/03-maintaining.md
View file
Open in desktop
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