Fixes to cherry-pick in [0.17-stable]

[bestander]

0.17.0

• Don't output list if all dependencies are up to date - 567f8af
• Fix expected manifest on global add Yarn 0.17.0 unexpected manifest error in linux #1855 16a5268
• ENOENT: no such file or directory, chmod - [0.17.0] Error while linking dependencies #1853 [0.17.0] Error chmod-ing .bin files on 'yarn install' #1823

---

0.17.2 branch cut

• Yarn global add doesn't add the binary [regression] [0.17.2] Yarn global add doesn't add the binary nor warn #1886 Fix global add linking issue #1889 b76ac93
• yarn install not generating missing lockfile - Not generating yarn.lock file as expected #1876 135fd87
• No such file file or directory, lstat - "No such file file or directory, lstat" for Yarn cache during package install on Windows #1834 error An unexpected error occurred: "ENOENT: no such file or directory, lstat '/Users/xxx/Library/Caches/Yarn/npm-webpack-stream-3.2.0-d679c2f1f964b5abae4c1f29d5cb695115deec7b'". #1836 [0.17.0] Cannot add module from github #1831 [0.17.0] Cannot add dependency in org/repo format #1818 Skip setting hash if hash was not set previously #1871 (1180f0f)
• node-pre-gyp: not found Regression between 0.16.1 and 0.17.0 when building package using node-gyp? #1838 yarn add grpc throws error [0.17.0] #1817

---

0.17.3 branch cut

• roadrunner.json .roadrunner.json error #1724 (4ce67f3)

---

0.17.4 branch cut

• bcrypt build regression [0.17] Regression: Native modules (node-gyp) not built correctly after using "yarn add" #1848 (fix 3f765c3)
• node-sass build artifact - Bug: postinstall/install script not being run on dependencies #1872 [0.17.0] Issues with node-sass #1832 (can't repro)
• install script + .npmrc [0.17.0] Regression: Doesn't run install script #1852 (no one can repro, something odd with .npmrc)

---

0.17.6 branch cut

• add a cache breaker to the yarn cache based on the current version to prevent dependency shifting (fix Add a cache breaker to roadrunner cache #1965)

---

0.17.7, 0.17.8 branch cut

• yarn install --verbose yarn install --verbose #763 (cbdef66)

---

0.17.9 branch cut

• Fixes race condition on yarn install mutex network Fixes race condition on yarn install mutex network #2092 718d4ed

---

0.17.10 branch cut

---- NOT CHERRY PICKED, WILL BE RELEASED IN 0.18

• Scoped package installation sometimes fails on Windows Scoped package installation sometimes fails on Windows #1861 (fix Resolve scoped package paths during linking on Windows #1866)
• authentication for scoped private registry tarballs Fix request authentication for scoped private registry tarballs #1666 Authentication with private registries #1318

[dbashford]

If this is you guys figuring out what needs to be prioritized for the next release... I think #1823 has made Yarn unusable for a lot of folks.

[bestander]

Thanks, @dbashford, yes, help with prioritization, fixes and tests is very much welcome

[cpojer]

Thanks @bestander for trying to be on top of this. I know it's hard with all the issues/PRs coming in. Once we get to better test coverage we should figure out how we can focus on making the project a bit less of a burden to maintain :)

[bestander]

0.17.3 is being deployed, please send more PRs and let us know what is the highest pri now

[KidkArolis]

Consider pulling in #1666, it fixes yarn for use with private authenticated registries.

[bestander]

@KidkArolis I've added it to the list but to the bottom considering that it is still in progress and is not a regression (right?).

[KidkArolis]

Thanks, nw.

[Daniel15]

I think the roadrunner.json issue is fairly important to fix.

[bestander]

Everything that people could consistently reproduce has been fixed and cherry-picked into 0.17.4 which is being released now.

[SimenB]

@bestander #761

[bestander]

@SimenB, I understand this is an ongoing issue and not a regression.

[SimenB]

It was made worse in 0.17. We had yarn --prod which worked, and with 0.17 it broke. My repro breaks in both 0.16 and 0.17 though

[bestander]

@SimenB, ok, we'll get this in

[owais]

Just tried 0.17.9 on OS X but it still doesn't seem to fix the private tarballs issue. Should I open another issue for this or did we not actually roll out the fix yet?

Trace:
  Error: http://npm.mycompany.com/@/@my-company/mypackage/_attachments/mypackage-3.7.2.tgz: invalid tar file
      at Extract.Parse._startEntry (/usr/local/Cellar/yarn/0.17.9/libexec/lib/node_modules/yarn/node_modules/tar/lib/parse.js:149:13)
      at Extract.Parse._process (/usr/local/Cellar/yarn/0.17.9/libexec/lib/node_modules/yarn/node_modules/tar/lib/parse.js:131:12)
      at BlockStream.<anonymous> (/usr/local/Cellar/yarn/0.17.9/libexec/lib/node_modules/yarn/node_modules/tar/lib/parse.js:47:8)
      at emitOne (events.js:96:13)
      at BlockStream.emit (events.js:188:7)
      at BlockStream._emitChunk (/usr/local/Cellar/yarn/0.17.9/libexec/lib/node_modules/yarn/node_modules/block-stream/block-stream.js:145:10)
      at BlockStream.flush (/usr/local/Cellar/yarn/0.17.9/libexec/lib/node_modules/yarn/node_modules/block-stream/block-stream.js:70:8)
      at BlockStream.end (/usr/local/Cellar/yarn/0.17.9/libexec/lib/node_modules/yarn/node_modules/block-stream/block-stream.js:66:8)
      at Extract.Parse.end (/usr/local/Cellar/yarn/0.17.9/libexec/lib/node_modules/yarn/node_modules/tar/lib/parse.js:86:23)
      at UnpackStream.onend (_stream_readable.js:511:10)

[bestander]

Hey guys, I'd like to not cherry-pick the last two:
Scoped package installation sometimes fails on Windows #1861 (fix #1866)
authentication for scoped private registry tarballs #1666 #1318

And release 0.18.0 with them during the weekend.
Cherry-picking got a bit harder with master branch diverging

[bestander]

0.18 released