Repository navigation
build!: drop support for EOL Django versions - #26
Merged
Merged
Conversation
BREAKING CHANGE: Django 4.2 reached end of life in April 2026 and is no longer supported. The minimum supported Django version is now 5.2 (LTS).
Lower the ruff/coverage pins to releases older than the 14-day cutoff so their exclude-newer-package entries are no longer needed.
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.
exclude-newercutoff (ruff >= 0.17.0, coverage >= 7.16.2), so their[tool.uv.exclude-newer-package]entries are no longer needed. The security-fix entries stay until 2026-11-09.Breaking change: the package now requires Django >= 5.2.