actions/setup-python
4
0
Fork 0
mirror of https://github.com/actions/setup-python.git synced 2025-11-07 05:26:56 +00:00
Code Activity Actions

Update to use 3.14 not 3.12 as an example for pre-release

Browse source
This commit is contained in:
Yaroslav Halchenko 2025-09-24 08:57:34 -04:00
parent 3b11caf218
commit c97bfe2182
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/advanced-usage.md
View file

@ -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