diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8a8f8f85028..76e704dacb1 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -152,7 +152,7 @@ By default git would use `CRLF` line endings which would cause the scripts to fa
 9. Wait for a long time, and it will get published. Don’t worry that it’s stuck. In the end the publish script will prompt for versions before publishing the packages.
 10. After publishing, create a GitHub Release with the same text as the changelog entry. See previous Releases for inspiration.
 
-Make sure to test the released version! If you want to be extra careful, you can publish a prerelease by running `npm run publish -- --canary=next --exact --cd-version patch --npm-tag=next` instead of `npm run publish`.
+Make sure to test the released version! If you want to be extra careful, you can publish a prerelease by running `npm run publish -- prepatch --canary --preid next --dist-tag next --npm-client npm --force-publish` instead of `npm run publish`.
 
 ---
 
diff --git a/package.json b/package.json
index ac8d1c0e8db..9763ceec6a6 100644
--- a/package.json
+++ b/package.json
@@ -26,7 +26,7 @@
     "globby": "^9.1.0",
     "husky": "^1.3.1",
     "jest": "24.7.1",
-    "lerna": "2.9.1",
+    "lerna": "3.13.2",
     "lerna-changelog": "~0.8.2",
     "lint-staged": "^8.0.4",
     "meow": "^5.0.0",
diff --git a/tasks/publish.sh b/tasks/publish.sh
index 56f2de6fb82..802d10cf518 100755
--- a/tasks/publish.sh
+++ b/tasks/publish.sh
@@ -48,4 +48,4 @@ if [ -z $CI ]; then
 fi
 
 # Go!
-NPM_CONFIG_OTP="$otp" ./node_modules/.bin/lerna publish --independent --npm-client=npm "$@"
+NPM_CONFIG_OTP="$otp" ./node_modules/.bin/lerna publish --npm-client=npm "$@"