hopefully travis automatically uses npm v3 because of node upgrade

alm-tools · Apr 20, 2016 · 5b8cca8 · 5b8cca8
1 parent 517a021
commit 5b8cca8
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 4 deletions.
diff --git a/.travis.yml b/.travis.yml
@@ -1,8 +1,6 @@
 language: node_js
 node_js:
-- '4.1'
-before_install:
-- if [[ `npm -v` != 3* ]]; then npm i -g npm@3; fi
+- '5'
 deploy:
   provider: npm
   email: [email protected]

diff --git a/docs/contributing/deployment-intenals.md b/docs/contributing/deployment-intenals.md
@@ -8,4 +8,3 @@ We have an npm `postversion` script setup to run `git push --follow-tags` which
 * Toggle switch on travis using https://travis-ci.org/
 * NPM deploy setup by simply running `travis setup npm` (you get `travis` from `gem install travis`). Then setup the API key using https://github.com/npm/npm/issues/8970#issuecomment-122854271
 * `all_branches` in `.travis.yml` is set to `true` because of https://github.com/travis-ci/travis-ci/issues/1675#issuecomment-37851765
-* Had to upgrade the travis `npm` to `v3` because of https://github.com/alm-tools/alm/issues/59. Done using https://github.com/travis-ci/travis-ci/issues/4653#issuecomment-194051953