notes for 0.5.0

docs/venvlink-and-pew.md

@@ -95,4 +95,5 @@ Type "help", "copyright", "credits" or "license" for more information.
 -  When using `activate` script created with `venvlink` (or python `venv`), the name of the active virtual environment is shown in parenthesis at the left side of the shell prompt.
 - When using `pew workon`, the virtual environment can be activated from anywhere using the ***name*** of the virtual environment. When using `venvlink`, the virtual environment can be activated using the ***`activate` script*** which is located the project folder (can also be called anywhere). 
 - When creating virtual environments, one must be in a project folder, to create a virtual environment with `venvlink`, but you can create virtual environment anywhere using `pew`. 
-- The activate script using `venvlink` will colorize the virtual environment name, if using Powershell.
+- The activate script using `venvlink` will colorize the virtual environment name, if using Powershell.
+- `venvlink` (0.5.0+) has support for automatically activating and deactivating virtual environments in Powershell using [venvlink-autoenv](https://github.com/np-8/venvlink-autoenv-powershell).

docs/venvlink-and-pipenv.md

@@ -25,7 +25,7 @@
 - With `venvlink`, one would activate the virtual environment using the `activate` script ("link") located in the project folder. The cwd can be anything when the `activate` script is ran.
 - With `venvlink` it is also possible to run the python executable directly with `<venv_folder>/<venv_name>/Scipts/python.exe ...`, if needed (as with when using `venv` without `venvlink`)
 -  It is also possible to use [`pew` with venvlink](venvlink-and-pew.md). (and activate virtual environments using `pew workon myproject`)
-
+  - `venvlink` (0.5.0+) has support for automatically activating and deactivating virtual environments in Powershell using [venvlink-autoenv](https://github.com/np-8/venvlink-autoenv-powershell).
 
 ## Changing virtual environments