Yarn should be available when lerna is run, and the publish command should be non-interactive.

We switch away from lerna thinking the package manager is jlpm since lerna has some hardcoded logic to deal with “yarn”

lerna.json

@@ -1,7 +1,12 @@
 {
   "lerna": "2.4.0",
   "version": "independent",
-  "npmClient": "jlpm",
+  "npmClient": "yarn",
   "registry": "https://registry.npmjs.org/",
-  "useWorkspaces": true
+  "useWorkspaces": true,
+  "command": {
+    "publish": {
+      "npmClientArgs": ["--non-interactive"]
+    }
+  }
 }