File tree Expand file tree Collapse file tree 3 files changed +37
-13
lines changed Expand file tree Collapse file tree 3 files changed +37
-13
lines changed Original file line number Diff line number Diff line change 1+ store : zeus
2+ targets :
3+ - name : github
4+ changelog : History.md
5+ - npm
Original file line number Diff line number Diff line change 1- branches :
2- only :
3- - master
41sudo : false
52language : node_js
63node_js :
@@ -9,7 +6,31 @@ node_js:
96 - " 6"
107 - " 7"
118 - " 8"
9+
1210cache :
1311 directories :
1412 - node_modules
13+
14+ branches :
15+ only :
16+ - master
17+
1518script : npm run test-full
19+
20+ matrix :
21+ include :
22+ - script : npm pack
23+ node_js : " 8"
24+ after_success :
25+ - npm install -g @zeus-ci/cli
26+ - zeus upload -t "application/tar+npm" *.tgz
27+
28+ notifications :
29+ webhooks :
30+ urls :
31+ - https://zeus.ci/hooks/b152d48c-d694-11e7-99e7-0a580a28020f/public/provider/travis/webhook
32+ on_success : always
33+ on_failure : always
34+ on_start : always
35+ on_cancel : always
36+ on_error : always
Original file line number Diff line number Diff line change 11## How to release raven-node:
2- * [ ] Run the manual memory tests in ` test/manual ` to make sure we didn't introduce a memory leak
3- * [ ] Consider whether any changes warrant additions to these tests
4- * [ ] Stop and think "What version number should this be according to SemVer?"
5- * [ ] Bump version number in ` package.json ` .
6- * [ ] Add an entry to the [ History] ( https://github.com/getsentry/raven-node/blob/master/History.md ) file.
7- * [ ] Commit new version, create a tag (` git tag -a v1.2.3 -m "Version 1.2.3" ` ). Push to GitHub (` git push --follow-tags ` ).
8- * [ ] ` $ npm publish ` to push to npm.
9- * [ ] Verify that ` npm install raven@1.2.3 ` works.
10- * [ ] Copy History entry into a new GH Release: https://github.com/getsentry/raven-node/releases
11- * [ ] glhf
2+
3+ * [ ] Run the manual memory tests in ` test/manual ` to make sure we didn't introduce a memory leak
4+ * [ ] Consider whether any changes warrant additions to these tests
5+ * [ ] Stop and think "What version number should this be according to SemVer?"
6+ * [ ] Add an entry to the [ History] ( https://github.com/getsentry/raven-node/blob/master/History.md ) file.
7+ * [ ] Bump version number in ` package.json ` using ` npm version -m [patch|minor|major] 'release: %s' ` .
8+ * [ ] Push to GitHub (` git push origin master --follow-tags ` ).
9+ * [ ] Once CI builds pass, ` sentry-probot ` will publish a release on npm and GitHub.
You can’t perform that action at this time.
0 commit comments