Partial version resolution doesn't search prereleases. There's an open feature request to change this: #2622

Python 3.14 have officially released.

Currently, new releases are not detected automatically but interested parties usually provide us with PRs within a day of a release (which we receive notifications of). There is a 3.14.0 PR, I'll merge it shortly.

Well, then what's the purpose to install new Python release or maintenance release using pyenv install if pyenv couldn't detect a new Python release or maintenance release ? But most probably just for easy managing different versions of Python ?

There's a dilemma to choose whether to download and install a new Python release or maintenance release from https://www.python.org directly, or to use pyenv to install a new Python release or maintenance release but need to accept with the delay.

I'm currently working on a script to automate detecting new CPython releases.

Well hopefully this can speed up detecting a new Python release or maintenance release.

Well I also found installing a new Python release or maintenance release using pyenv will actually perform a compilation which takes some time to complete instead of just installing the Python binaries immediately just like downloading the Python macOS DMG file from https://www.python.org ?