|
| 1 | +## v5.0.3 (2017-06-05) |
| 2 | + |
| 3 | +Happy Monday, y'all! We've got another npm release for you with the fruits of |
| 4 | +our ongoing bugsquashing efforts. You can expect at least one more this week, |
| 5 | +but probably more -- and as we announced last week, we'll be merging fixes more |
| 6 | +rapidly into the `npmc` canary so you can get everything as soon as possible! |
| 7 | + |
| 8 | +Hope y'all are enjoying npm5 in the meantime, and don't hesitate to file issues |
| 9 | +for anything you find! The goal is to get this release rock-solid as soon as we |
| 10 | +can. 💚 |
| 11 | + |
| 12 | +* [`6e12a5cc0`](https://github.com/npm/npm/commit/6e12a5cc022cb5a157a37df7283b6d7b3d49bdab) |
| 13 | + Bump several dependencies to get improvements and bugfixes: |
| 14 | + * `cacache`: content files (the tarballs) are now read-only. |
| 15 | + * `pacote`: fix failing clones with bad heads, send extra TLS-related opts to proxy, enable global auth configurations and `_auth`-based auth. |
| 16 | + * `ssri`: stop crashing with `can't call method find of undefined` when running into a weird `opts.integrity`/`opts.algorithms` conflict during verification. |
| 17 | + ([@zkat](https://github.com/zkat)) |
| 18 | +* [`89cc8e3e1`](https://github.com/npm/npm/commit/89cc8e3e12dad67fd9844accf4d41deb4c180c5c) |
| 19 | + [#16917](https://github.com/npm/npm/pull/16917) |
| 20 | + Send `ca`, `cert` and `key` config through to network layer. |
| 21 | + ([@colinrotherham](https://github.com/colinrotherham)) |
| 22 | +* [`6a9b51c67`](https://github.com/npm/npm/commit/6a9b51c67ba3df0372991631992748329b84f2e7) |
| 23 | + [#16929](https://github.com/npm/npm/pull/16929) |
| 24 | + Send `npm-session` header value with registry requests again. |
| 25 | + ([@zarenner](https://github.com/zarenner)) |
| 26 | +* [`662a15ab7`](https://github.com/npm/npm/commit/662a15ab7e790e87f5e5a35252f05d5a4a0724a1) |
| 27 | + Fix `npm doctor` so it stop complaining about read-only content files in the |
| 28 | + cache. |
| 29 | + ([@zkat](https://github.com/zkat)) |
| 30 | +* [`191d10a66`](https://github.com/npm/npm/commit/191d10a6616d72e26d89fd00f5a4f6158bfbc526) |
| 31 | + [#16918](https://github.com/npm/npm/pull/16918) |
| 32 | + Clarify prepublish deprecation message. |
| 33 | + ([@Hirse](https://github.com/Hirse)) |
| 34 | + |
| 35 | +## v5.0.2 (2017-06-02) |
| 36 | + |
| 37 | +Here's another patch release, soon after the other! |
| 38 | + |
| 39 | +This particular release includes a slew of fixes to npm's git support, which was |
| 40 | +causing some issues for a chunk of people, specially those who were using |
| 41 | +self-hosted/Enterprise repos. All of those should be back in working condition |
| 42 | +now. |
| 43 | + |
| 44 | +There's another shiny thing you might wanna know about: npm has a Canary release |
| 45 | +now! The `npm5` experiment we did during our beta proved to be incredibly |
| 46 | +successful: users were able to have a tight feedback loop between reports and |
| 47 | +getting the bugfixes they needed, and the CLI team was able to roll out |
| 48 | +experimental patches and have the community try them out right away. So we want |
| 49 | +to keep doing that. |
| 50 | + |
| 51 | +From now on, you'll be able to install the 'npm canary' with `npm i -g npmc`. |
| 52 | +This release will be a separate binary (`npmc`. Because canary. Get it?), which |
| 53 | +will update independently of the main CLI. Most of the time, this will track |
| 54 | +`release-next` or something close to it. We might occasionally toss experimental |
| 55 | +branches in there to see if our more adventurous users run into anything |
| 56 | +interesting with it. For example, the current canary (`npmc@5.0.1-canary.6`) |
| 57 | +includes an [experimental multiproc |
| 58 | +branch](https://github.com/npm/npm/pull/16633) that parallelizes tarball |
| 59 | +extraction across multiple processes. |
| 60 | + |
| 61 | +If you find any issues while running the canary version, please report them and |
| 62 | +let us know it came from `npmc`! It would be tremendously helpful, and finding |
| 63 | +things early is a huge reason to have it there. Happy hacking! |
| 64 | + |
| 65 | +### A NOTE ABOUT THE ISSUE TRACKER |
| 66 | + |
| 67 | +Just a heads up: We're preparing to do a massive cleanup of the issue tracker. |
| 68 | +It's been a long time since it was something we could really keep up with, and |
| 69 | +we didn't have a process for dealing with it that could actually be sustainable. |
| 70 | + |
| 71 | +We're still sussing the details out, and we'll talk about it more when we're |
| 72 | +about to do it, but the plan is essentially to close old, abandoned issues and |
| 73 | +start over. We will also [add some automation](https://github.com/probot) around |
| 74 | +issue management so that things that we can't keep up with don't just stay |
| 75 | +around forever. |
| 76 | + |
| 77 | +Stay tuned! |
| 78 | + |
| 79 | +### GIT YOLO |
| 80 | + |
| 81 | +* [`1f26e9567`](https://github.com/npm/npm/commit/1f26e9567a6d14088704e121ebe787c38b6849a4) |
| 82 | + `pacote@2.7.27`: Fixes installing committishes that look like semver, even |
| 83 | + though they're not using the required `#semver:` syntax. |
| 84 | + ([@zkat](https://github.com/zkat)) |
| 85 | +* [`85ea1e0b9`](https://github.com/npm/npm/commit/85ea1e0b9478551265d03d545e7dc750b9edf547) |
| 86 | + `npm-package-arg@5.1.1`: This includes the npa git-parsing patch to make it so |
| 87 | + non-hosted SCP-style identifiers are correctly handled. Previously, npa would |
| 88 | + mangle them (even though hosted-git-info is doing the right thing for them). |
| 89 | + ([@zkat](https://github.com/zkat)) |
| 90 | + |
| 91 | +### COOL NEW OUTPUT |
| 92 | + |
| 93 | +The new summary output has been really well received! One downside that reared |
| 94 | +its head as more people used it, though, is that it doesn't really tell you |
| 95 | +anything about the toplevel versions it installed. So, if you did `npm i -g |
| 96 | +foo`, it would just say "added 1 package". This patch by |
| 97 | +[@rmg](https://github.com/rmg) keeps things concise while still telling you |
| 98 | +what you got! So now, you'll see something like this: |
| 99 | + |
| 100 | +``` |
| 101 | +$ npm i -g foo bar |
| 102 | ++ foo@1.2.3 |
| 103 | ++ bar@3.2.1 |
| 104 | +added 234 packages in .005ms |
| 105 | +``` |
| 106 | + |
| 107 | +* [`362f9fd5b`](https://github.com/npm/npm/commit/362f9fd5bec65301082416b4292b8fe3eb7f824a) |
| 108 | + [#16899](https://github.com/npm/npm/pull/16899) |
| 109 | + For every package that is given as an argument to install, print the name and |
| 110 | + version that was actually installed. |
| 111 | + ([@rmg](https://github.com/rmg)) |
| 112 | + |
| 113 | +### OTHER BUGFIXES |
| 114 | + |
| 115 | +* [`a47593a98`](https://github.com/npm/npm/commit/a47593a98a402143081d7077d2ac677d13083010) |
| 116 | + [#16835](https://github.com/npm/npm/pull/16835) |
| 117 | + Fix a crash while installing with `--no-shrinkwrap`. |
| 118 | + ([@jacknagel](https://github.com/jacknagel)) |
| 119 | + |
| 120 | +### DOC UPATES |
| 121 | + |
| 122 | +* [`89e0cb816`](https://github.com/npm/npm/commit/89e0cb8165dd9c3c7ac74d531617f367099608f4) |
| 123 | + [#16818](https://github.com/npm/npm/pull/16818) |
| 124 | + Fixes a spelling error in the docs. Because the CLI team has trouble spelling |
| 125 | + "package", I guess. |
| 126 | + ([@ankon](https://github.com/ankon)) |
| 127 | +* [`c01fbc46e`](https://github.com/npm/npm/commit/c01fbc46e151bcfb359fd68dd7faa392789b4f55) |
| 128 | + [#16895](https://github.com/npm/npm/pull/16895) |
| 129 | + Remove `--save` from `npm init` instructions, since it's now the default. |
| 130 | + ([@jhwohlgemuth](https://github.com/jhwohlgemuth)) |
| 131 | +* [`80c42d218`](https://github.com/npm/npm/commit/80c42d2181dd4d1b79fcee4e9233df268dfb30b7) |
| 132 | + Guard against cycles when inflating bundles, as symlinks are bundles now. |
| 133 | + ([@iarna](https://github.com/iarna)) |
| 134 | +* [`7fe7f8665`](https://github.com/npm/npm/commit/7fe7f86658798db6667df89afc75588c0e43bc94) |
| 135 | + [#16674](https://github.com/npm/npm/issues/16674) |
| 136 | + Write the builtin config for `npmc`, not just `npm`. This is hardcoded for npm |
| 137 | + self-installations and is needed for Canary to work right. |
| 138 | + ([@zkat](https://github.com/zkat)) |
| 139 | + |
| 140 | +### DEP UPDATES |
| 141 | + |
| 142 | +* [`63df4fcdd`](https://github.com/npm/npm/commit/63df4fcddc7445efb50cc7d8e09cdd45146d3e39) |
| 143 | + [#16894](https://github.com/npm/npm/pull/16894) |
| 144 | + [`node-gyp@3.6.2`](https://github.com/nodejs/node-gyp/blob/master/CHANGELOG.md#v362-2017-06-01): |
| 145 | + Fixes an issue parsing SDK versions on Windows, among other things. |
| 146 | + ([@refack](https://github.com/refack)) |
| 147 | +* [`5bb15c3c4`](https://github.com/npm/npm/commit/5bb15c3c4f0d7d77c73fd6dafa38ac36549b6e00) |
| 148 | + `read-package-tree@5.1.6`: Fixes some racyness while reading the tree. |
| 149 | + ([@iarna](https://github.com/iarna)) |
| 150 | +* [`a6f7a52e7`](https://github.com/npm/npm/commit/a6f7a52e7) |
| 151 | + `aproba@1.1.2`: Remove nested function declaration for speed up |
| 152 | + ([@mikesherov](https://github.com/mikesherov)) |
| 153 | + |
| 154 | +## v5.0.1 (2017-05-31): |
| 155 | + |
| 156 | +Hey y'all! Hope you're enjoying the new npm! |
| 157 | + |
| 158 | +As you all know, fresh software that's gone through major overhauls tends to |
| 159 | +miss a lot of spots the old one used to handle well enough, and `npm@5` is no |
| 160 | +exception. The CLI team will be doing faster release cycles that go directly to |
| 161 | +the `latest` tag for a couple of weeks while 5 stabilizes a bit and we're |
| 162 | +confident the common low-hanging fruit people are running into are all taken |
| 163 | +care of. |
| 164 | + |
| 165 | +With that said: this is our first patch release! The biggest focus is fixing up |
| 166 | +a number of git-related issues that folks ran into right out the door. It also |
| 167 | +fixes other things, like some proxy/auth-related issues, and even has a neat |
| 168 | +speed boost! (You can expect more speed bumps in the coming releases as pending |
| 169 | +work starts landing, too!) |
| 170 | + |
| 171 | +Thanks everyone who's been reporting issues and submitting patches! |
| 172 | + |
| 173 | +### BUGFIXES |
| 174 | + |
| 175 | +* [`e61e68dac`](https://github.com/npm/npm/commit/e61e68dac4fa51c0540a064204a75b19f8052e58) |
| 176 | + [#16762](https://github.com/npm/npm/pull/16762) |
| 177 | + Make `npm publish` obey the `--tag` flag again. |
| 178 | + ([@zkat](https://github.com/zkat)) |
| 179 | +* [`923fd58d3`](https://github.com/npm/npm/commit/923fd58d312f40f8c17b232ad1dfc8e2ff622dbd) |
| 180 | + [#16749](https://github.com/npm/npm/pull/16749) |
| 181 | + Speed up installations by nearly 20% by... removing one line of code. (hah) |
| 182 | + ([@mikesherov](https://github.com/mikesherov)) |
| 183 | +* [`9aac984cb`](https://github.com/npm/npm/commit/9aac984cbbfef22182ee42b51a193c0b47146ad6) |
| 184 | + Guard against a particular failure mode for a bug still being hunted down. |
| 185 | + ([@iarna](https://github.com/iarna)) |
| 186 | +* [`80ab521f1`](https://github.com/npm/npm/commit/80ab521f18d34df109de0c5dc9eb1cde5ff6d7e8) |
| 187 | + Pull in dependency updates for various core deps: |
| 188 | + * New `pacote` fixes several git-related bugs. |
| 189 | + * `ssri` update fixes crash on early node@4 versions. |
| 190 | + * `make-fetch-happen` update fixes proxy authentication issue. |
| 191 | + * `npm-user-validate` adds regex for blocking usernames with illegal chars. |
| 192 | + ([@zkat](https://github.com/zkat)) |
| 193 | +* [`7e5ce87b8`](https://github.com/npm/npm/commit/7e5ce87b84880c7433ee4c07d2dd6ce8806df436) |
| 194 | + `pacote@2.7.26`: |
| 195 | + Fixes various other git issues related to commit hashes. |
| 196 | + ([@zkat](https://github.com/zkat)) |
| 197 | +* [`acbe85bfc`](https://github.com/npm/npm/commit/acbe85bfc1a68d19ca339a3fb71da0cffbf58926) |
| 198 | + [#16791](https://github.com/npm/npm/pull/16791) |
| 199 | + `npm view` was calling `cb` prematurely and giving partial output when called |
| 200 | + in a child process. |
| 201 | + ([@zkat](https://github.com/zkat)) |
| 202 | +* [`ebafe48af`](https://github.com/npm/npm/commit/ebafe48af91f702ccefc8c619d52fed3b8dfd3c7) |
| 203 | + [#16750](https://github.com/npm/npm/pull/16750) |
| 204 | + Hamilpatch the Musical: Talk less, complete more. |
| 205 | + ([@aredridel](https://github.com/aredridel)) |
| 206 | + |
| 207 | +### DOCUMENTATION |
| 208 | + |
| 209 | +* [`dc2823a6c`](https://github.com/npm/npm/commit/dc2823a6c5fc098041e61515c643570819d059d2) |
| 210 | + [#16799](https://github.com/npm/npm/pull/16799) |
| 211 | + Document that `package-lock.json` is never allowed in tarballs. |
| 212 | + ([@sonicdoe](https://github.com/sonicdoe)) |
| 213 | +* [`f3cb84b44`](https://github.com/npm/npm/commit/f3cb84b446c51d628ee0033cdf13752c15b31a29) |
| 214 | + [#16771](https://github.com/npm/npm/pull/16771) |
| 215 | + Fix `npm -l` usage information for the `test` command. |
| 216 | + ([@grawlinson](https://github.com/grawlinson)) |
| 217 | + |
| 218 | +### OTHER CHANGES |
| 219 | + |
| 220 | +* [`661262309`](https://github.com/npm/npm/commit/66126230912ab5ab35287b40a9908e036fa73994) |
| 221 | + [#16756](https://github.com/npm/npm/pull/16756) |
| 222 | + remove unused argument |
| 223 | + ([@Aladdin-ADD](https://github.com/Aladdin-ADD)) |
| 224 | +* [`c3e0b4287`](https://github.com/npm/npm/commit/c3e0b4287ea69735cc367aa7bb7e7aa9a6d9804b) |
| 225 | + [#16296](https://github.com/npm/npm/pull/16296) |
| 226 | + preserve same name convention for command |
| 227 | + ([@desfero](https://github.com/desfero)) |
| 228 | +* [`9f814831d`](https://github.com/npm/npm/commit/9f814831d330dde7702973186aea06caaa77ff31) |
| 229 | + [#16757](https://github.com/npm/npm/pull/16757) |
| 230 | + remove unused argument |
| 231 | + ([@Aladdin-ADD](https://github.com/Aladdin-ADD)) |
| 232 | +* [`3cb843239`](https://github.com/npm/npm/commit/3cb8432397b3666d88c31131dbb4599016a983ff) |
| 233 | + minor linter fix |
| 234 | + ([@zkat](https://github.com/zkat)) |
| 235 | + |
1 | 236 | ## v5.0.0 (2017-05-25) |
2 | 237 |
|
3 | 238 | Wowowowowow npm@5! |
|
0 commit comments