You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello @ssbarnea 👋,
This request is similar to issue #571. We will consider enhancing the parsing logic for the python-version-file input to include support for .tool-versions files.
We appreciate your feedback and will evaluate this feature for a future enhancement. In the meantime, please feel free to provide any additional details or use cases to help us better understand the impact and prioritize this feature.
Thank you!
Description:
Opposed to setup-nodejs official action, python one is not able to read
.tool-versions
files to determine the version of python to be used.Action version:
latest
Platform:
Runner type:
Tools version:
Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
Expected behavior:
A description of what you expected to happen.
Actual behavior:
Be able to make use of
.tool-versions
files$ cat .tool-versions direnv 2.34.0 nodejs 18.19.1 # asdf install task latest task 3.37.2 yarn 1.22.19 python 3.12.7
The text was updated successfully, but these errors were encountered: