⚙️ Drop Python 3.8 and 3.9 support, and update CI coverage to Python 3.10 through 3.14. - #156
Merged
Conversation
…3.10 through 3.14.
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.
Summary
Why this change
The recent dependency update means the project can no longer resolve its environment on Python 3.8.
pipenv lock now pulls packages whose current releases require newer Python versions, including dependencies that declare Requires-Python >=3.10. As a result, the CI lock step fails on Python 3.8 before tests even run.
Because the project currently follows floating dependency resolution for several packages, keeping Python 3.8 or 3.9 support would require adding and maintaining older version pins specifically for those interpreters. This change instead aligns the declared support range with the dependency set that resolves today.
Validation