update changelog

Author: ktalebian

changelog/v4.md

@@ -1,6 +1,8 @@
-## 4.x - Beta
+## 4.0.0 (May 17th, 2021)
 
-Create Flex Plugin 4.x uses the [Twilio Flex Plugins API](https://www.twilio.com/docs/flex/plugins/api) to manage your Flex Plugins, create versions, and define which plugins the Flex UI will load during initialization via an API.  
+Refer to [Twilio Flex Docs](https://www.twilio.com/docs/flex/developer/plugins/cli) to be up-to-date with the latest features being built on the CLI.
+
+Create Flex Plugin 4.0.0 uses the [Twilio Flex Plugins API](https://www.twilio.com/docs/flex/plugins/api) to manage your Flex Plugins, create versions, and define which plugins the Flex UI will load during initialization via an API.  
 
 It completely removes the dependency on `react-scripts` and instead uses native Webpack to build and serve your plugins locally.
 
@@ -22,6 +24,8 @@ $ twilio flex:plugins:upgrade-plugin --install
 
 This script should automatically upgrade your plugin to the latest version. 
 
+## Manual Upgrade
+
 To manually upgrade to version 4.x, modify your `package.json`:
 
 ```json
@@ -30,7 +34,7 @@ To manually upgrade to version 4.x, modify your `package.json`:
     "postinstall": "flex-plugin pre-script-check"
   },
   "dependencies": {
-    "flex-plugin-scripts": "^4.2.7-beta.0",
+    "flex-plugin-scripts": "^4.0.0",
     "react": "16.5.2",
     "react-dom": "16.5.2"
   },
@@ -39,9 +43,6 @@ To manually upgrade to version 4.x, modify your `package.json`:
   }
 }
 ```
-
-Please use `npm view flex-plugin-scripts dist-tags.beta` to find the current latest beta version and use that instead of `4.2.7-beta.0` as show above.
-
 If you are currently using `craco.config.js`, please refer to the next section [Breaking Changes](#breaking-changes) on migrating it.
 
 You may also need to update your `public/appConfig.js` and update the `pluginService`:
@@ -78,7 +79,7 @@ module.exports = (config, { isProd, isDev, isTest }) => {
 
 Upgrading from v1/v2 will, unfortunately, include a period of downtime. Your contact-center will either have the same plugin running twice or the plugin missing from it (this period will only be at most 1 minute long). Therefore, it is recommended to do this migration when you don't expect high usage of your contact center.
 
-First, upgrade the plugin locally using `$ twilio flex:plugins:upgrade --beta` from the guide above.  
+First, upgrade the plugin locally using `$ twilio flex:plugins:upgrade` from the guide above.  
 
 Next, decide if you prefer to have the plugin show twice or not at all. You'll need to deploy/release using the CLI and delete the plugin from [Twilio Console Assets](https://www.twilio.com/console/assets). Unfortunately, these two steps must be done manually. 
 
@@ -88,7 +89,7 @@ It is recommended that you `deploy` (using `twilio flex:plugins:deploy`) your pl
 
 Upgrading from v3 is simple and has no downtime. 
 
-1. Upgrade the plugin locally using `$ twilio flex:plugins:upgrade --beta` from the guide above.  
+1. Upgrade the plugin locally using `$ twilio flex:plugins:upgrade` from the guide above.  
 2. Deploy and register the plugin using `$ twilio flex:plugins:deploy` and `$ twilio flex:plugins:release`
 3. Remove the v0.0.0 plugin from v3 using `$ twilio flex:plugins:upgrade --cleanup`
 

lerna.json

@@ -2,5 +2,5 @@
   "packages": [
     "packages/*"
   ],
-  "version": "4.9.1-beta.0"
+  "version": "4.10.0-alpha.0"
 }