Alex Eagle 026b7e34b3 build: update yarn version (#27193) ... Some engineers were already on Yarn 0.10.x which was permitted by the range in our package.json#engines However this introduced 'integrity sha512' lines into the yarn.lock files. Then when engineers use yarn 0.9 (in particular, Bazel did this) then the lock files get tons of meaningless edits. We could force everyone back to yarn 0.9 but this commit chooses to instead advance everyone past 0.10 PR Close #27193		2018-11-21 07:46:22 -08:00
..
browserstack	ci: clean up CI logging, folding, add build time logging, and improve error handling (#14425)	2017-03-02 00:22:24 -08:00
ci	build: update yarn version (#27193)	2018-11-21 07:46:22 -08:00
git	fix: missing semi-colon and empty line (#26945)	2018-11-05 11:37:55 -08:00
github	build: add more labels to review-pr script (#26493)	2018-10-16 14:36:28 -07:00
jenkins	fix(build): make perf tests work again	2015-02-27 15:22:19 -08:00
release	build: release scripts should use bazel from yarn (#26899)	2018-11-20 10:44:34 -08:00
sauce	build: switch from npm to yarn (#19328)	2017-09-22 13:20:52 -07:00
windows	build: fix windows scripts (#23121)	2018-07-12 16:42:56 -04:00
build-packages-dist.sh	build: use bazel version from node modules (#26691)	2018-10-30 16:19:13 -04:00