fix(conf): scope Python version constraint to github-actions manager#14
Merged
fix(conf): scope Python version constraint to github-actions manager#14
Conversation
The previous matchPackageNames: ["python"] rule had no manager context, so it may not have matched the uses-with dep tracked by the github-actions manager. Also tightened allowedVersions from "<3.14" to "<=3.13" to avoid semver pre-release ambiguity with tags like 3.14.0-<build>.
The matchManagers: ["github-actions"] scope was too narrow — the constraint should apply to all managers (pyproject.toml, .python-version, workflows, etc.). The real fix was tightening allowedVersions from "<3.14" to "<=3.13" to avoid semver pre-release ambiguity with tags like 3.14.0-<build>.
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.
Problem
Renovate kept re-opening a Python `3.13 → 3.14` PR even though `allowedVersions: "<3.14"` was set.
Root cause: semver pre-release ambiguity. Python versions in `actions/python-versions` are tagged as `3.14.0-18313368925`. In strict semver, `3.14.0-` is a pre-release of `3.14.0` and evaluates as `< 3.14.0`, so the range `<3.14` allows it through.
Fix
Changed `allowedVersions: "<3.14"` → `"<=3.13"` to unambiguously exclude all 3.14.x versions regardless of tag suffixes. No manager restriction — the constraint applies across all managers: GitHub Actions workflows, `pyproject.toml`, `.python-version`, etc.
Test plan