ci: hard pin python to <3.14 to fix build loop#69
Merged
JacksonFergusonDev merged 2 commits intomainfrom Feb 16, 2026
Merged
Conversation
Add a targeted rule for the "python-version" datasource. This specifically prevents Renovate from attempting to upgrade the "requires-python" field in pyproject.toml to 3.14+, ensuring project metadata remains consistent with our runtime pins.
Change `requires-python` from `~=3.13.0` to `">=3.13,<3.14"`. While the tilde operator is valid, using an explicit upper bound (<3.14) is unambiguous and prevents automated tools from interpreting the constraint as "movable" to the 3.14 release series.
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
1 participant
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.
Description
This PR fixes the CI failure where Renovate effectively "broke" the build by upgrading the project's Python requirement to 3.14 while the CI environment remained pinned to 3.13.
Changes
pyproject.toml:requires-pythonto">=3.13,<3.14".~=3.13.0allowed Renovate to propose~=3.14.3as a "minor" upgrade. The new explicit range strictly forbids 3.14, ensuringuvis never forced to look for an interpreter that doesn't exist in our CI..github/renovate.json:matchDatasources: ["python-version"].requires-pythonupdates differently than standard dependencies. This rule explicitly tells the bot that metadata updates for Python are also restricted to the3.13.*regex pattern.Context
Renovate previously opened a PR changing
requires-pythonto~=3.14.3. Because we successfully pinned our GitHub Actions runner to 3.13.12 in the last PR, this created a conflict:This change aligns the project metadata (pyproject.toml) with the runtime reality (GitHub Actions), creating a consistent 3.13 environment.