Repository navigation
fix(security): upgrade Django to supported LTS - #45
Merged
Merged
Conversation
|
KageRyo
commented
Oct 23, 2026
KageRyo
left a comment
KageRyo
left a comment
Owner
Author
There was a problem hiding this comment.
Reviewed this exact head against the authorized security and test cleanup scope. The local verification listed in the description passed; all current hosted checks are successful or conditional skips. Remaining upstream compatibility limits are disclosed in the description where applicable.
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
Upgrade Django5.2.18 and remove three tautological list-type assertions while retaining schema and authorization checks.
Validation
python -m pytest --collect-only -qgit diff --checkDjango system checks, in-memory migrations and admin login smoke passed. Existing live HTTP tests were collected only; they were not run against a real service.
No application release/version bump, database migration, model retraining or research-result change is included.