VIRTUAL_ENV is set to wrong directory when using pyproject-file config

[MarkusSintonen]

We are getting warnings: warning: VIRTUAL_ENV=/home/runner/work/my_repo/my_proj/.venv does not match the project environment path .venv and will be ignored

The VIRTUAL_ENV seems to be pointing to wrong place which is not under the defined pyproject:

    - uses: astral-sh/setup-uv@v5
      with:
        pyproject-file: ./my_subproject/pyproject.toml

Shouldnt the VIRTUAL_ENV in this case be pointing to VIRTUAL_ENV=/home/runner/work/my_repo/my_proj/my_subproject/.venv?

Issue seems to be originating here

setup-uv/src/setup-uv.ts

Line 165 in 2098017

core.exportVariable("VIRTUAL_ENV", path.resolve(".venv"));

which was recently changed here #224 But that PR is not considering that the VIRTUAL_ENV should be relative to the defined pyproject-file directory, right?

[MarkusSintonen]

How should this anyways work with projects having multiple sub-pyprojects?

[eifinger]

When I implemented the pyproject-file input I was not thinking about monorepos.

How should this anyways work with projects having multiple sub-pyprojects?

tl;dr: It doesn't.

This action needs breaking changes in order to fix this bug. Might take me a while to find a way which doesn't lead to more breaking changes a few weeks after...

[MarkusSintonen]

Would it be possible to have option to skipping the setting of this env?

[eifinger]

If you DON'T use python-version it will be skipped