Bump version to 0.22.1

CHANGELOG.md

@@ -1,3 +1,10 @@
+## 0.22.1 (2019/9/19)
+* __Breaking Change__: Remove snippet support `plain text`
+* __Feature__: [Add setting to display request name as response tab title](https://github.com/Huachao/vscode-restclient/pull/400) ([@lochstar](https://github.com/lochstar))
+* __Feature__: [Allow environment variables to reference shared variables](https://github.com/Huachao/vscode-restclient/pull/409) ([@snackb](https://github.com/snackb))
+* __Improvement__: Add CSP for response and code snippet webviews
+* __Improvement__: Support multipart mime types of request
+
 ## 0.22.0 (2019/7/31)
 * __Feature__: [Add support for `GraphQL`](https://github.com/Huachao/vscode-restclient/pull/384) ([@ferronrsmith](https://github.com/ferronrsmith))
 * __Feature__: [Add new system variable - local machine environment variable](https://github.com/Huachao/vscode-restclient/pull/366) ([@mtnrbq](https://github.com/mtnrbq))

README.md

@@ -371,21 +371,23 @@ The reference syntax of system and custom variables types has a subtle differenc
 Custom variables can cover different user scenarios with the benefit of environment variables, file variables, and request variables. Environment variables are mainly used for storing values that may vary in different environments. Since environment variables are directly defined in Visual Studio Code setting file, they can be referenced across different `http` files. File variables are mainly used for representing values that are constant throughout the `http` file. Request variables are used for the chaining requests scenarios which means a request needs to reference some part(header or body) of another request/response in the _same_ `http` file, imagine we need to retrieve the auth token dynamically from the login response, request variable fits the case well. Both file and request variables are defined in the `http` file and only have __File Scope__.
 
 #### Environment Variables
-For environment variables, each environment comprises a set of key value pairs defined in setting file, key and value are variable name and value respectively. Only variables defined in selected environment and shared environment are available to you. Below is a sample piece of setting file for custom environments and environment level variables:
+For environment variables, each environment comprises a set of key value pairs defined in setting file, key and value are variable name and value respectively. Only variables defined in selected environment and shared environment are available to you. You can also reference the variables in shard environment with `{{$shared variableName}}` syntax in your active environment. Below is a sample piece of setting file for custom environments and environment level variables:
 ```json
 "rest-client.environmentVariables": {
     "$shared": {
-        "version": "v1"
+        "version": "v1",
+        "prodToken": "foo",
+        "nonProdToken": "bar"
     },
     "local": {
         "version": "v2",
         "host": "localhost",
-        "token": "test token",
+        "token": "{{$shared nonProdToken}}",
         "secretKey": "devSecret"
     },
     "production": {
         "host": "example.com",
-        "token": "product token",
+        "token": "{{$shared prodToken}}",
         "secretKey" : "prodSecret"
     }
 }

package.json

@@ -2,7 +2,7 @@
   "name": "rest-client",
   "displayName": "REST Client",
   "description": "REST Client for Visual Studio Code",
-  "version": "0.22.0",
+  "version": "0.22.1",
   "publisher": "humao",
   "author": {
     "name": "Huachao Mao",