Upgrade version to 1.1.5

README.md

@@ -15,14 +15,14 @@ If all you need is default Poetry, simply add this to your workflow:
 
 ```yaml
 - name: Install Poetry
-  uses: snok/install-poetry@v1.1.4
+  uses: snok/install-poetry@v1.1.5
 ```
 
 If you want to set Poetry config settings, or install a specific version, you can specify inputs
 
 ```yaml
 - name: Install and configure Poetry
-  uses: snok/install-poetry@v1.1.4
+  uses: snok/install-poetry@v1.1.5
   with:
     version: 1.1.6
     virtualenvs-create: true
@@ -49,7 +49,7 @@ or just to make changes to the Poetry config *after* invoking the action -
 you can do so in a subsequent step, like this
 
 ```yaml
-- uses: snok/install-poetry@v1.1.4
+- uses: snok/install-poetry@v1.1.5
 - run: poetry config experimental.new-installer false
 ```
 
@@ -96,7 +96,7 @@ jobs:
       #  -----  install & configure poetry  -----      
       #----------------------------------------------
       - name: Install Poetry
-        uses: snok/install-poetry@v1.1.4
+        uses: snok/install-poetry@v1.1.5
         with:
           virtualenvs-create: true
           virtualenvs-in-project: true
@@ -192,7 +192,7 @@ jobs:
       #  -----  install & configure poetry  -----      
       #----------------------------------------------
       - name: Install Poetry
-        uses: snok/install-poetry@v1.1.4
+        uses: snok/install-poetry@v1.1.5
         with:
           virtualenvs-create: true
           virtualenvs-in-project: true
@@ -259,7 +259,7 @@ jobs:
       #  -----  install & configure poetry  -----      
       #----------------------------------------------
     - name: Install Poetry
-      uses: snok/install-poetry@v1.1.4
+      uses: snok/install-poetry@v1.1.5
       with:
         virtualenvs-create: true
         virtualenvs-in-project: true
@@ -360,7 +360,7 @@ jobs:
         with:
           python-version: 3.9
       - name: Install Poetry
-        uses: snok/install-poetry@v1.1.4
+        uses: snok/install-poetry@v1.1.5
         with:
           virtualenvs-create: true
           virtualenvs-in-project: true
@@ -395,7 +395,7 @@ All of the examples we've added use these Poetry settings
 
 ```yaml
 - name: Install Poetry
-  uses: snok/install-poetry@v1.1.4
+  uses: snok/install-poetry@v1.1.5
   with:
     virtualenvs-create: true
     virtualenvs-in-project: true

pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "install-poetry"
-version = "1.1.4"
+version = "1.1.5"
 description = ""
 authors = ["Sondre Lillebø Gundersen <sondrelg@live.no.com>"]
 maintainers = ["Jonas Krüger Svensson <jonasks@hotmail.com>"]

scripts/v1.2/main.sh

@@ -36,9 +36,9 @@ if [ "$os" == "Windows" ]; then
   path="C:/Users/runneradmin/AppData/Roaming/Python/Scripts/poetry.exe"
 
   # Configure Poetry
-  poetry config virtualenvs.create "$venv_create"
-  poetry config virtualenvs.in-project "$venv_in_project"
-  poetry config virtualenvs.path "$venv_path"
+  $path config virtualenvs.create "$venv_create"
+  $path config virtualenvs.in-project "$venv_in_project"
+  $path config virtualenvs.path "$venv_path"
 
   # Add system path, so the executable is made available in the next workflow steps
   echo "C:/Users/runneradmin/AppData/Roaming/Python/Scripts/" >> $GITHUB_PATH