Merge tag 'v1.2.0' into develop

v1.2.0

Author: connesy

CHANGELOG.md

@@ -1,9 +1,9 @@
 # Changelog
 
-## Unreleased
+## [v1.2.0](https://github.com/SallingGroup-AI-and-ML/venv-cli/releases/tag/v1.2.0) (2023-08-04)
 
 From this release forward, this project follows the `Git Flow` branching model. To reflect this, the default development branch have been renamed `develop`, and the `main` branch is now only for tagged releases.
-To read more about Git Flow, see (https://nvie.com/posts/a-successful-git-branching-model/). Also see [README](https://github.com/SallingGroup-AI-and-ML/venv-cli/blob/develop/README.md#git-flow) for branch naming conventions.
+To read more about Git Flow, see (https://nvie.com/posts/a-successful-git-branching-model/). Also see [README](https://github.com/SallingGroup-AI-and-ML/venv-cli/blob/v1.2.0/README.md#git-flow) for branch naming conventions.
 
 * Changed github test workflow to reflect new branch naming conventions.
 * Added better, context-based bash completions.

src/venv-cli/venv.sh

@@ -9,7 +9,7 @@ _yellow="\033[01;33m"
 _red="\033[31m"
 
 # Version number has to follow pattern "^v\d+\.\d+\.\d+.*$"
-_version="v1.1.0"
+_version="v1.2.0"
 
 # Valid VCS URL environment variable pattern
 # https://peps.python.org/pep-0610/#specification