Yarn: Fixes to cherry-pick in [0.17-stable]

Created on 15 Nov 2016  路  16Comments  路  Source: yarnpkg/yarn

0.17.0

- [x] ENOENT: no such file or directory, chmod - https://github.com/yarnpkg/yarn/issues/1853 #1823

0.17.2 branch cut

- [x] node-pre-gyp: not found https://github.com/yarnpkg/yarn/issues/1838 #1817

0.17.3 branch cut

- [x] roadrunner.json #1724 (https://github.com/yarnpkg/yarn/commit/4ce67f3d5da3ba99c3e8718100883e9f145ce125)

0.17.4 branch cut

  • [x] bcrypt build regression #1848 (fix https://github.com/yarnpkg/yarn/commit/3f765c354306bd8e6ca22b3bb333542d1a8fd6e2)
  • [x] node-sass build artifact - #1872 #1832 (can't repro)

- [x] install script + .npmrc https://github.com/yarnpkg/yarn/issues/1852 (no one can repro, something odd with .npmrc)

0.17.6 branch cut

- [x] add a cache breaker to the yarn cache based on the current version to prevent dependency shifting (fix #1965)

0.17.7, 0.17.8 branch cut

- [x] yarn install --verbose #763 (cbdef6639664d1bd098d459a06dd2168b3a6db4b)

0.17.9 branch cut

- [x] Fixes race condition on yarn install mutex network #2092 718d4ed9ccbd1b4c945991ba353708a2d111db43

0.17.10 branch cut

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

  • [x] Scoped package installation sometimes fails on Windows #1861 (fix #1866)
  • [x] authentication for scoped private registry tarballs #1666 #1318

Most helpful comment

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.

All 16 comments

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.

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

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 :)

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

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

@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?).

Thanks, nw.

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

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

@bestander #761

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

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

@SimenB, ok, we'll get this in

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)

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

0.18 released

Was this page helpful?
0 / 5 - 0 ratings