settings.virtualenvs.in-project does not exist

[snok]

settings.virtualenvs.in-project does not exist

[sondrelg]

Are you saying you're unable to run the action with Poetry v1 or above? Can you add your workflow specification?

[miigotu]

I agree that the prefix is not needed (or allowed) in 1.0.4 or so +

I can pip install some different poetry versions later in clean environments to verify.

I've been using something like this for awhile:

poetry config virtualenvs.in-project true
poetry config virtualenvs.path .venv

https://python-poetry.org/docs/configuration/#virtualenvsin-project

[miigotu]

@chanansh are you sure you aren't setting that yourself in the workflow? Please show your workflow file.

In this project, it is called like this:

poetry config virtualenvs.in-project "$venv_in_project"

where $venv_in_project is true or false, determined by your setting in the with parameter on the workflow.

This is how it is done:

jobs:
  install-poetry:
    name: Install and configure Poetry
    uses: snok/install-poetry@v1
    with:
        version: 1.1.13
        virtualenvs-create: true
        virtualenvs-in-project: true
        virtualenvs-path: .venv
        installer-parallel: false

I think your workflow must call poetry config settings.virtualenvs.in-project true in a later step, after poetry is installed, or you are using an outdated version of the action.

I suggest you also use dependabot or some other workflow to keep your actions dependencies updated:

.github/dependabot.yml

version: 2
updates:
- package-ecosystem: github-actions
  directory: "/"
  schedule:
    interval: daily