Update to latest pyenv and/or provide support for specifying the required version

[abingham]

I'm facing action failures because of what appears to be a bug in the version of pyenv that's being used. It seems to be related to the bug mentioned here. I'd like to be able to use a different version of pyenv in my action.

Is there a way with pyenv-action to specify the version of pyenv that should be used? I poked through the code and didn't see anything; it seems to be hardcoded to whatever's in default.ts. But if I missed something and there's a way to specify it, that would probably solve my problem.

If there's not a way to specify the version, can we upgrade the version in defaults.ts and/or provide a way to override it? I'll be happy to provide a patch for the former. The latter will probably require work from someone who knows the codebase better them me.

[rob-smallshire]

The pyenv version has been updated in main branch. I worked around the lack of a new numbered release of this action by specifying gabrielfalcao/pyenv-action@main as the GitHub action version. This is not ideal, but it allowed progress.

[xiaoyao9184]

not work still use 2.4.20

Run gabrielfalcao/pyenv-action@main
  with:
    default: 3.8
    versions: 3.5.10, 3.6.15, 3.7.17, 3.8.20, 3.9.21, 3.10.16, 3.11.11
    command: pip install -U pip
downloading https://github.com/pyenv/pyenv/archive/v2.[4](https://github.com/xiaoyao9184/ansible-docker/actions/runs/13960931025/job/39081950397#step:3:4).20.zip
/usr/bin/unzip -o -q /opt/hostedtoolcache/pyenv-archive.zip/2.4.20/x64/pyenv-archive.zip

[nedbat]

I would love to use this action for nightly CPython testing. But it's hardcoded to a version of pyenv that doesn't know about 3.15-dev yet. I would like to use the latest version of pyenv. Can we enable that? Why hardcode to a particular version?