diff options
| author | isaacs <i@izs.me> | 2013-12-17 21:04:19 +0400 |
|---|---|---|
| committer | isaacs <i@izs.me> | 2013-12-17 21:04:30 +0400 |
| commit | e10c223eb6b861b8aabb9c062298062e5b85d0d9 (patch) | |
| tree | e78fc51432ffd8f4433bf02c7e263f5442071263 /deps/npm/html/doc/README.html | |
| parent | 97738994e0bc2f3255659ca8f27e43a90aa0a24e (diff) | |
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/html/doc/README.html')
| -rw-r--r-- | deps/npm/html/doc/README.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html index 253d24fb357..4c5817df05f 100644 --- a/deps/npm/html/doc/README.html +++ b/deps/npm/html/doc/README.html @@ -239,7 +239,7 @@ will no doubt tell you to put the output in a gist or email.</p> <ul><li><a href="cli/npm.html">npm(1)</a></li><li><a href="misc/npm-faq.html">npm-faq(7)</a></li><li><a href="cli/npm-help.html">npm-help(1)</a></li><li><a href="misc/npm-index.html">npm-index(7)</a></li></ul> </div> -<p id="footer"><a href="../doc/README.html">README</a> — npm@1.3.19</p> +<p id="footer"><a href="../doc/README.html">README</a> — npm@1.3.20</p> <script> ;(function () { var wrapper = document.getElementById("wrapper") |