summaryrefslogtreecommitdiff
path: root/deps/npm/man/man3
diff options
context:
space:
mode:
authorisaacs <i@izs.me>2013-12-17 09:04:19 -0800
committerisaacs <i@izs.me>2013-12-17 09:04:30 -0800
commite10c223eb6b861b8aabb9c062298062e5b85d0d9 (patch)
treee78fc51432ffd8f4433bf02c7e263f5442071263 /deps/npm/man/man3
parent97738994e0bc2f3255659ca8f27e43a90aa0a24e (diff)
downloadnode-new-e10c223eb6b861b8aabb9c062298062e5b85d0d9.tar.gz
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.
Diffstat (limited to 'deps/npm/man/man3')
-rw-r--r--deps/npm/man/man3/npm.32
1 files changed, 1 insertions, 1 deletions
diff --git a/deps/npm/man/man3/npm.3 b/deps/npm/man/man3/npm.3
index 984cb9b782..917c298131 100644
--- a/deps/npm/man/man3/npm.3
+++ b/deps/npm/man/man3/npm.3
@@ -21,7 +21,7 @@ npm\.load([configObject], function (er, npm) {
.fi
.
.SH "VERSION"
-1.3.19
+1.3.20
.
.SH "DESCRIPTION"
This is the API documentation for npm\.