Hi@yarikoptic, thanks for improving the documentation!
Since Python 3.14 is now the current pre-release, could you please update both the explanatory paragraph and the matrix example to use "3.14" as the pre-release version instead of 3.12. This will make the example more relevant and accurately demonstrate how allow-prereleases works with an actual pre-release, rather than referencing 3.12, which is already generally available.

Since here I am not adding a new documentation but rather providing minor tune up to already existing wording, which was potentially added whenallow-prereleases was added, IMHO would be best to keep exampleas is. Switching to 3.14 would invalidate added "in the past" and would then require such a PR later to make it again factually correct.

Hi@yarikoptic, To keep the original wording intact, it is suggested to only update the version number from 3.12 to 3.14 in the paragraph, like this:

Let’s say that Python 3.14 is not generally available, the following workflow will fallback to the most recent pre-release of Python 3.14.

And in the matrix, update the version list to:
python_version: ["3.14"]

This way, the example provides a concrete and current reference for configuring workflows with a real pre-release version, making it more practical and helpful for users.