Repository navigation
Run the linters on the latest Python 3.14 patch release - #917
Merged
Merged
Conversation
GitHub is moving ubuntu-latest to Ubuntu 26.04, and actions/python-versions has no 3.14.0 build for 26.04 (3.14.6+ only), so setup-python fails. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI fails on every PR that lands on an Ubuntu 26.04 runner:
GitHub is moving
ubuntu-latestto Ubuntu 26.04 between October 19 and November 19, 2026.actions/python-versionsonly builds 3.14.6 and later for 26.04, and the matrix has pinned the exact3.14.0since #693. The first failure was #916 today; every earlier run had landed on 24.04.python: '3.14.0'→'3.14', which resolves to the latest 3.14 patch release (3.14.9 today) on both 24.04 and 26.04v1→v2: the cached./venvpoints at the 3.14.0 interpreter path, so a cache hit would break under a new patch releaseRequested by Martin Breuss in maintenance triage.
🤖 Generated with Claude Code