doc: update changelog for npm@5.0.2

1 files changed, 119 insertions, 0 deletions

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 16a17beea..478ee4674 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,122 @@
+## v5.0.2 (2017-06-02)
+
+Here's another patch release, soon after the other!
+
+This particular release includes a slew of fixes to npm's git support, which was
+causing some issues for a chunk of people, specially those who were using
+self-hosted/Enterprise repos. All of those should be back in working condition
+now.
+
+There's another shiny thing you might wanna know about: npm has a Canary release
+now! The `npm5` experiment we did during our beta proved to be incredibly
+successful: users were able to have a tight feedback loop between reports and
+getting the bugfixes they needed, and the CLI team was able to roll out
+experimental patches and have the community try them out right away. So we want
+to keep doing that.
+
+From now on, you'll be able to install the 'npm canary' with `npm i -g npmc`.
+This release will be a separate binary (`npmc`. Because canary. Get it?), which
+will update independently of the main CLI. Most of the time, this will track
+`release-next` or something close to it. We might occasionally toss experimental
+branches in there to see if our more adventurous users run into anything
+interesting with it. For example, the current canary (`npmc@5.0.1-canary.6`)
+includes an [experimental multiproc
+branch](https://github.com/npm/npm/pull/16633) that parallelizes tarball
+extraction across multiple processes.
+
+If you find any issues while running the canary version, please report them and
+let us know it came from `npmc`! It would be tremendously helpful, and finding
+things early is a huge reason to have it there. Happy hacking!
+
+### A NOTE ABOUT THE ISSUE TRACKER
+
+Just a heads up: We're preparing to do a massive cleanup of the issue tracker.
+It's been a long time since it was something we could really keep up with, and
+we didn't have a process for dealing with it that could actually be sustainable.
+
+We're still sussing the details out, and we'll talk about it more when we're
+about to do it, but the plan is essentially to close old, abandoned issues and
+start over. We will also [add some automation](https://github.com/probot) around
+issue management so that things that we can't keep up with don't just stay
+around forever.
+
+Stay tuned!
+
+### GIT YOLO
+
+* [`1f26e9567`](https://github.com/npm/npm/commit/1f26e9567a6d14088704e121ebe787c38b6849a4)
+  `pacote@2.7.27`: Fixes installing committishes that look like semver, even
+  though they're not using the required `#semver:` syntax.
+  ([@zkat](https://github.com/zkat))
+* [`85ea1e0b9`](https://github.com/npm/npm/commit/85ea1e0b9478551265d03d545e7dc750b9edf547)
+  `npm-package-arg@5.1.1`: This includes the npa git-parsing patch to make it so
+  non-hosted SCP-style identifiers are correctly handled. Previously, npa would
+  mangle them (even though hosted-git-info is doing the right thing for them).
+  ([@zkat](https://github.com/zkat))
+
+### COOL NEW OUTPUT
+
+The new summary output has been really well received! One downside that reared
+its head as more people used it, though, is that it doesn't really tell you
+anything about the toplevel versions it installed. So, if you did `npm i -g
+foo`, it would just say "added 1 package". This patch by
+[@rmg](https://github.com/rmg) keeps things concise while still telling you
+what you got! So now, you'll see something like this:
+
+```
+$ npm i -g foo bar
++ foo@1.2.3
++ bar@3.2.1
+added 234 packages in .005ms
+```
+
+* [`362f9fd5b`](https://github.com/npm/npm/commit/362f9fd5bec65301082416b4292b8fe3eb7f824a)
+  [#16899](https://github.com/npm/npm/pull/16899)
+  For every package that is given as an argument to install, print the name and
+  version that was actually installed.
+  ([@rmg](https://github.com/rmg))
+
+### OTHER BUGFIXES
+
+* [`a47593a98`](https://github.com/npm/npm/commit/a47593a98a402143081d7077d2ac677d13083010)
+  [#16835](https://github.com/npm/npm/pull/16835)
+  Fix a crash while installing with `--no-shrinkwrap`.
+  ([@jacknagel](https://github.com/jacknagel))
+
+### DOC UPATES
+
+* [`89e0cb816`](https://github.com/npm/npm/commit/89e0cb8165dd9c3c7ac74d531617f367099608f4)
+  [#16818](https://github.com/npm/npm/pull/16818)
+  Fixes a spelling error in the docs. Because the CLI team has trouble spelling
+  "package", I guess.
+  ([@ankon](https://github.com/ankon))
+* [`c01fbc46e`](https://github.com/npm/npm/commit/c01fbc46e151bcfb359fd68dd7faa392789b4f55)
+  [#16895](https://github.com/npm/npm/pull/16895)
+  Remove `--save` from `npm init` instructions, since it's now the default.
+  ([@jhwohlgemuth](https://github.com/jhwohlgemuth))
+* [`80c42d218`](https://github.com/npm/npm/commit/80c42d2181dd4d1b79fcee4e9233df268dfb30b7)
+  Guard against cycles when inflating bundles, as symlinks are bundles now.
+  ([@iarna](https://github.com/iarna))
+* [`7fe7f8665`](https://github.com/npm/npm/commit/7fe7f86658798db6667df89afc75588c0e43bc94)
+  [#16674](https://github.com/npm/npm/issues/16674)
+  Write the builtin config for `npmc`, not just `npm`. This is hardcoded for npm
+  self-installations and is needed for Canary to work right.
+  ([@zkat](https://github.com/zkat))
+
+### DEP UPDATES
+
+* [`63df4fcdd`](https://github.com/npm/npm/commit/63df4fcddc7445efb50cc7d8e09cdd45146d3e39)
+  [#16894](https://github.com/npm/npm/pull/16894)
+  [`node-gyp@3.6.2`](https://github.com/nodejs/node-gyp/blob/master/CHANGELOG.md#v362-2017-06-01):
+  Fixes an issue parsing SDK versions on Windows, among other things.
+  ([@refack](https://github.com/refack))
+* [`5bb15c3c4`](https://github.com/npm/npm/commit/5bb15c3c4f0d7d77c73fd6dafa38ac36549b6e00)
+  `read-package-tree@5.1.6`: Fixes some racyness while reading the tree.
+  ([@iarna](https://github.com/iarna))
+* [`a6f7a52e7`](https://github.com/npm/npm/commit/a6f7a52e7)
+  `aproba@1.1.2`: Remove nested function declaration for speed up
+  ([@mikesherov](https://github.com/mikesherov))
+
 ## v5.0.1 (2017-05-31):
 
 Hey y'all! Hope you're enjoying the new npm!