Comparing version 0.1.1 to 0.1.2
@@ -0,1 +1,7 @@ | ||
0.1.2 / 2015-08-04 | ||
================== | ||
* Is now compliant with git-extras version 3.0.0 | ||
0.1.1 / 2015-08-04 | ||
@@ -2,0 +8,0 @@ ================== |
{ | ||
"name": "ez-release", | ||
"version": "0.1.1", | ||
"version": "0.1.2", | ||
"description": "Release npm packages easily", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
@@ -5,6 +5,35 @@ # ez-release | ||
`ez-release` is a command that combines common tasks about package publishments. | ||
1. Generate changelog via `git changelog` command from [git-extras][1]. | ||
2. Update the `version` field in `package.json`. | ||
3. Commit these two files. | ||
4. Tag current version. | ||
5. Push commit and tag onto remote. | ||
6. Publish the package. | ||
Here's the list of commands that will be executed. | ||
```bash | ||
$ ez-release patch --dryrun | ||
$ npm version patch --no-git-tag-version | ||
$ git changelog --tag 0.1.2 | ||
$ git add package.json | ||
$ git commit -m 0.1.2 | ||
$ git tag v0.1.2 | ||
$ git push origin | ||
$ git push origin --tags | ||
$ npm publish | ||
``` | ||
Running all the steps listed above manually can be tiresome and error prone. | ||
So `ez-release` come to rescue. All you have to do is specify the new version, | ||
whether it's a major, minor, or patch version bump. Then edit the generated | ||
changelog. You are good to go. | ||
## Install | ||
```bash | ||
$ brew install git-extras # tested with version 3.0.0 | ||
$ npm install ez-release -g | ||
@@ -42,1 +71,4 @@ ``` | ||
``` | ||
[1]: https://github.com/tj/git-extras |
Sorry, the diff of this file is not supported yet
7513
73