Kat Marchán
aff3acf268
deps: upgrade to npm 2.14.7
...
PR-URL: https://github.com/nodejs/node/pull/3299
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
2015-10-09 18:50:00 -07:00
Forrest L Norvell
f166cdecf1
deps: upgrade npm to 2.7.4
2015-03-30 14:34:39 -07:00
Forrest L Norvell
af1bf49852
deps: upgrade npm to 2.5.1
...
PR-URL: https://github.com/iojs/io.js/pull/738
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
2015-02-06 18:38:36 +01:00
Forrest L Norvell
faf34ffbd3
deps: upgrade npm to 2.4.1
...
PR-URL: https://github.com/iojs/io.js/pull/663
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
2015-01-31 18:57:30 +01:00
Forrest L Norvell
e79ccee168
npm: upgrade to v2.1.18
...
PR-URL: https://github.com/iojs/io.js/pull/266
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
2015-01-08 23:49:03 +01:00
Timothy J Fontaine
9fad8958df
deps: upgrade npm to 2.0.0
2014-09-24 17:15:10 -07:00
Timothy J Fontaine
daca803e9e
npm: Update to 1.4.28
2014-09-16 15:38:50 -07:00
Timothy J Fontaine
1223cafea6
npm: Upgrade to v1.4.21
2014-07-31 09:05:30 -07:00
isaacs
2a741f2d12
npm: upgrade to 1.3.21
2013-12-17 14:33:52 -08:00
isaacs
e10c223eb6
npm: upgrade to 1.3.20
...
The 1.3.19 release had a critical bug: any packages published with it
could not be installed, because the shasum would be incorrect.
Thankfully, 1.3.19 was published using 1.3.19, so could not be installed
by any users! However, if it goes out as part of a Node.js release,
then obviously that would be a problem.
2013-12-17 09:04:30 -08:00
isaacs
97738994e0
npm: Upgrade to 1.3.19
2013-12-16 23:09:16 -08:00
