Skip to content

Improve wording and "fix example" (remove 3.13) on testing against pre-release #979

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 14, 2025
Merged

Improve wording and "fix example" (remove 3.13) on testing against pre-release #979

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3b11caf
Improve wording and "fix example" (remove 3.13) on testing against pr…
yarikoptic Dec 5, 2024
c97bfe2
Update to use 3.14 not 3.12 as an example for pre-release
yarikoptic Sep 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/advanced-usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 python 3.12 is not generally available, the following workflow will 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:
Expand All @@ -597,7 +597,7 @@ jobs:
fail-fast: false
matrix:
os: [Ubuntu, Windows, macOS]
python_version: ["3.11", "3.12", "3.13"]
python_version: ["3.14"]
Copy link
Contributor Author

@yarikoptic yarikoptic Sep 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gowridurgad like this?

if you see how to improve further, please use suggestions
image
so we converge faster.


steps:
- uses: actions/checkout@v4
Expand Down