v4.5.0 bricks CI/CD pipeline if there is any (even though unused) pyproject.toml using poetry in a subfolder with invalid references

[Alyxion]

Description:

• Before publishing my Python package SciStag to pypi I am (locally) using a script which creates a new poetry environment, installs a wheel I manually built with poetry build and verifies if all tests also run fine in this environment.
• This script and the pyproject.toml it uses is in a nested folder and never used on GitHub as this is just a final, manual verification step for me
• The wheel this script requires (through a reference in the pyproject.toml) does also not exist in GitHub nor is it intended to being build there (yet)
• Since the update 4.5.0 your action unfortunately finds the pyproject.toml by crawling through all sub folders as it seems. poetry list fails b.c. it can of course not work with the wheel missing

Action version:
4.5

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:
Python 3.9, Python 3.10

Repro steps:

• Trying to build SciStag/SciStag@562e8a2 (using 4.5.0) will fail with
  

• Trying the same with any prior version e.g. 4.4.0 will succeed
  

Expected behavior:

• It should not deep dive into nested folders or ignore invalid pyproject.toml files or it should be possible to define directories which shall be ignored

Actual behavior:

• The action fails as soon as it finds the first invalid pyproject.toml, irrelevant how deeply hidden it is in the folder structure

[e-korolevskii]

Hello @Alyxion! Thank you for reporting this!
We will investigate the issue and get back to you as soon as we have updates

[oranav]

@Alyxion Please try to specify a specific cache-dependency-path. The default value is **/poetry.lock which obviously looks for all Poetry projects in all subfolders.

In your case, specifying cache-dependency-path: poetry.lock should do the trick.

[e-korolevskii]

Hello @Alyxion, did you manage to try this workaround?

[Alyxion]

Sorry for the late response but the cold caught me a bit.

Thank you for the hint @oranav, with the limited cache-dependency path everything works as expected and w/o errors with the 4.5.0:

[dmitry-shibanov]

Hello @Alyxion. It looks like the issue was resolved. In this case I'm going to close it. If you have any concerns feel free to ping us.