aboutsummaryrefslogtreecommitdiff
path: root/deps/npm/node_modules/npm-registry-client/lib/publish.js
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/node_modules/npm-registry-client/lib/publish.js
parent97738994e0bc2f3255659ca8f27e43a90aa0a24e (diff)
downloadandroid-node-v8-e10c223eb6b861b8aabb9c062298062e5b85d0d9.tar.gz
android-node-v8-e10c223eb6b861b8aabb9c062298062e5b85d0d9.tar.bz2
android-node-v8-e10c223eb6b861b8aabb9c062298062e5b85d0d9.zip
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/node_modules/npm-registry-client/lib/publish.js')
-rw-r--r--deps/npm/node_modules/npm-registry-client/lib/publish.js2
1 files changed, 1 insertions, 1 deletions
diff --git a/deps/npm/node_modules/npm-registry-client/lib/publish.js b/deps/npm/node_modules/npm-registry-client/lib/publish.js
index 9404a129db..90dec546b8 100644
--- a/deps/npm/node_modules/npm-registry-client/lib/publish.js
+++ b/deps/npm/node_modules/npm-registry-client/lib/publish.js
@@ -65,7 +65,7 @@ function putFirst (data, tardata, stat, username, email, cb) {
data._id = data.name+"@"+data.version
data.dist = data.dist || {}
- data.dist.shasum = crypto.createHash("sha1").update(tardata).digest("hex")
+ data.dist.shasum = crypto.createHash("sha1").update(tardata, 'base64').digest("hex")
data.dist.tarball = url.resolve(registry, tbURI)
.replace(/^https:\/\//, "http://")