From c97bfe2182fadc03d5ab70d2fc967d5803b4d174 Mon Sep 17 00:00:00 2001 From: Yaroslav Halchenko Date: Wed, 24 Sep 2025 08:57:34 -0400 Subject: [PATCH] Update to use 3.14 not 3.12 as an example for pre-release --- docs/advanced-usage.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/advanced-usage.md b/docs/advanced-usage.md index 0ecebd83..8f1b714d 100644 --- a/docs/advanced-usage.md +++ b/docs/advanced-usage.md @@ -586,8 +586,8 @@ If the runner is not able to access github.com, any Python versions requested du The `allow-prereleases` flag defaults to `false`. If `allow-prereleases` is set to `true`, the action will allow falling back to pre-release versions of Python when a matching GA version of Python is not available. This allows for example to simplify reuse of `python-version` as an input of nox for pre-releases of Python by not requiring manipulation of the `3.y-dev` specifier. -For CPython, `allow-prereleases` will only have effect for `x.y` version range (e.g. `3.12`). -Let's say that in the past, when python 3.12 was not yet generally available, the following workflow would have fallback to the most recent pre-release of python 3.12: +For CPython, `allow-prereleases` will only have effect for `x.y` version range (e.g. `3.14`). +Let's say that in the past, when python 3.14 was not yet generally available, the following workflow would have fallback to the most recent pre-release of python 3.14: ```yaml jobs: test: @@ -597,7 +597,7 @@ jobs: fail-fast: false matrix: os: [Ubuntu, Windows, macOS] - python_version: ["3.11", "3.12"] + python_version: ["3.14"] steps: - uses: actions/checkout@v4