Merge pull request #6213 from chaseadamsio/patch-1

add migrating doc with update gatsby related deps

docs/docs/migrating-from-v1-to-v2.md

@@ -64,7 +64,7 @@ You can start with a few of the most important steps - install Gatsby v2 depende
 
 ## Update Gatsby version
 
-Update your `package.json` to use the pre-release versions of Gatsby and any related packages.
+Update your `package.json` to use the pre-release versions of Gatsby.
 
 `package.json`
 
@@ -78,6 +78,20 @@ Update your `package.json` to use the pre-release versions of Gatsby and any rel
 
 > Note: Gatsby v2 is in pre-release so you may encounter further breaking changes.
 
+## Update Gatsby related packages
+
+Update your `package.json` to use the pre-release versions of Gatsby related packages. Any package name that starts with `gatsby-` should be upgraded to use the `next` version. Note, this only applies to plugins managed in the gatsbyjs/gatsby repo. If you're using community plugins, they might not be upgraded yet. Check their repo for the status. Many plugins won't actually need upgraded so they very well might keep working. For example:
+
+`package.json`
+
+```json
+"dependencies": {
+    "gatsby-plugin-google-analytics": "next",
+    "gatsby-plugin-netlify": "next",
+    "gatsby-plugin-sass": "next",
+}
+```
+
 ## Manually install React
 
 In v1, the `react` and `react-dom` packages were included as part of the `gatsby` package. They are now `peerDependencies` so you are required to install them into your project.