Merge branch 'develop' into release/2.0

Author: connesy

.github/workflows/run_tests.yml

@@ -5,8 +5,9 @@ name: Linting and tests
 
 on:
   push:
-    branches: [ "main", "release/*" ]
+    branches: [ "main" ]
   pull_request:
+    branches: [ "main", "release/**", "develop" ]
 
 permissions:
   contents: read

CHANGELOG.md

@@ -5,6 +5,8 @@
 ### Major changes
 * `venv sync` has been removed. Use `venv install <requirements>.lock` instead. [#17](https://github.com/SallingGroup-AI-and-ML/venv-cli/pull/17)
 
+## [v1.4.0](https://github.com/SallingGroup-AI-and-ML/venv-cli/releases/tag/v1.4.0) (2023-10-30)
+
 ### Minor changes
 * `venv sync` command marked as deprecated with removal planned for `v2.0`. Use `venv install <requirements>.lock` instead. [#14](https://github.com/SallingGroup-AI-and-ML/venv-cli/pull/14)
 * `venv install` now runs `venv clear` before installation. This ensures that the enrivonment doesn't end up with orphaned packages after making changes to `requirements.txt`. [#9](https://github.com/SallingGroup-AI-and-ML/venv-cli/issues/9)

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.3.0"
+_version="v1.4.0"
 
 # Valid VCS URL environment variable pattern
 # https://peps.python.org/pep-0610/#specification