提交 01d7a616 编写于 作者: M Matthew Andrews

Enable releasing fetch via a tag alone

上级 9b1ddc9e
language: node_js
script: make test
before_deploy:
- npm-prepublish --verbose
deploy:
provider: npm
email: "replace-with-email"
api_key:
secure: "replace-with-encrypted-api-key"
on:
all_branches: true
tags: true
repo: github/fetch
......@@ -6,24 +6,14 @@ This project follows [semver](http://semver.org/). So if you are making a bug
fix, only increment the patch level "1.0.x". If any new files are added, a
minor version "1.x.x" bump is in order.
### Make a release commit
### Make a release
To prepare the release commit:
To prepare the release:
1. Edit the [bower.json](https://github.com/github/fetch/blob/master/bower.json)
`version` value.
2. Change the npm [package.json](https://github.com/github/fetch/blob/master/package.json)
`version` value to match.
3. Make a single commit with the description as "Fetch 1.x.x".
4. Finally, tag the commit with `v1.x.x`.
1. Tag the commit with `v1.x.x`.
```
$ git pull
$ vim bower.json
$ vim package.json
$ git add bower.json package.json
$ git commit -m "Fetch 1.x.x"
$ git tag v1.x.x
$ git push
$ git push --tags
```
{
"name": "fetch",
"version": "0.4.0",
"main": "fetch.js",
"devDependencies": {
"es6-promise": "1.0.0",
......
{
"name": "fetch",
"version": "0.4.0",
"main": "fetch.js",
"private": true,
"devDependencies": {
"bower": "1.3.8",
"jshint": "2.5.2",
"node-qunit-phantomjs": "0.2.2"
"node-qunit-phantomjs": "0.2.2",
"npm-prepublish": "1.0.1"
}
}
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册