The npm blog has been discontinued.
Updates from the npm team are now published on the GitHub Blog and the GitHub Changelog.
v5.0.4 (2017-06-13)
Hey y'all. This is another minor patch release with a variety of little fixes we’ve been accumulating~
f0a37ace9Fixnpm doctorwhen hitting registries withoutping. (@zkat)64f0105e8Fix invalid format error when setting cache-related headers. ([@Kat Marchán](https://github.com/Kat Marchán))d2969c80eFix spuriousEINTEGRITYissue. (@zkat)800cb2b4e#17076 Use legacyfromfield to improve upgrade experience from legacy shrinkwraps and installs. (@zkat)4100d47ea#17007 Restore loose semver parsing to match older npm behavior when running into invalid semver ranges in dependencies. (@zkat)35316cce2#17005 Emulate npm@4’s behavior of simply marking the peerDep as invalid, instead of crashing. (@zkat)e7e8ee5c5#16937 Workaround for separate bug whererequestedwas somehow null. (@forivall)2d9629bb2Better logging output for git errors. (@zkat)2235aea73More scp-url fixes: parsing only worked correctly when a committish was present. (@zkat)80c33cf5eStandardize package permissions on tarball extraction, instead of using perms from the tarball. This matches previous npm behavior and fixes a number of incompatibilities in the wild. (@zkat)2b1e40efbLimit shallow cloning to hosts which are known to support it. (@zkat)