Python 3.15.0 lands in actions/python-versions for GitHub Actions
A short link-blog post dated 10 October 2026 reports that Python 3.15.0, the stable release, has been added to the actions/python-versions repository on GitHub.
The practical consequence is spelled out in the post: you can now add "3.15" to a GitHub Actions testing matrix and run your tests against the new Python 3.15.0 release.
The author calls it "a bit of a niche link" but says he had been waiting for it for a couple of days. To avoid checking by hand, he told ChatGPT to do it with this prompt: "Clone https://github.com/actions/python-versions and git pull once an hour until they add the stable 3.15 - then tell me about it". In other words, the check was a clone of the repository and a pull once an hour until the stable 3.15 appeared.
That is the whole item: one release-availability update, plus a small example of delegating a polling chore to a chatbot.
Key facts
- Python 3.15.0, the stable release, has been added to the actions/python-versions repository.
- With that in place, "3.15" can be added to a GitHub Actions testing matrix to run tests against Python 3.15.0.
- The author says he had been waiting for this for a couple of days.
- He told ChatGPT to clone the repository and git pull once an hour until the stable 3.15 appeared, then tell him.
Why it matters
Until a Python version is listed in actions/python-versions, it cannot be requested by name in a GitHub Actions testing matrix. Per the post, that has now changed for the stable 3.15.0 release, so projects can start running their test suites against it in CI. It is a small, routine milestone, and the author himself calls the link niche.
Who it affects
Python developers and maintainers who test their code with GitHub Actions and want to confirm compatibility with Python 3.15. Anyone not running CI matrices on GitHub Actions has no reason to care.
How to use it
Add "3.15" to the Python versions in your GitHub Actions testing matrix. The post gives no further setup steps. As a side note, the author's polling prompt to ChatGPT (clone the repository, git pull once an hour until the stable 3.15 appears, then report back) is a pattern others could reuse for similar waits.
How solid is it
This is a first-person link-blog note, brief and direct. The claim itself is simple: Python 3.15.0 was added to the repository, and "3.15" can now go in a testing matrix. The post does not say whether ChatGPT actually performed the check or notified the author, and no date or time is given for when 3.15.0 was added to the repository.
Risks and caveats
The post describes no changes, features or fixes in Python 3.15, so it says nothing about what might break when you switch the matrix over. It also gives no date for when Python 3.15.0 itself was released or when it landed in the repository. Treat it as a pointer to check the repository and your own CI results, not as a compatibility report.
“Bit of a niche link, but I've been waiting for this for a couple of days - I even told ChatGPT to check for it”
— Link blog post, 10 October 2026