chore: upgrade to Django 5.2 LTS #1431
Merged
Conversation
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
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #1431 +/- ##
==========================================
- Coverage 94.81% 91.20% -3.61%
==========================================
Files 338 232 -106
Lines 20053 9939 -10114
==========================================
- Hits 19013 9065 -9948
+ Misses 1040 874 -166
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 106 files with indirect coverage changes 🚀 New features to boost your workflow:
|
B-Whitt
force-pushed
the
django-50-upgrade
branch
3 times, most recently
from
607216f to
06750d6
Compare
Contributor
|
@B-Whitt can you look into the failing e2e tests? |
- Add FORMS_URLFIELD_ASSUME_HTTPS setting - Update channels to 4.1.x - Django 5.0.14 installed via dependency resolution - Django 5.2 LTS (support until April 2028) - drf-spectacular 0.29.x - channels 4.3.x - django-rq 3.2.x (requires rq 2.x) - rq 2.6.x - rq-scheduler 0.14.x (compatible with rq 2.x) - django-filter 25.2 - Update documentation URLs to Django 5.2 Note: DRF remains at 3.15.x due to django-ansible-base constraint (requires DRF <3.16 for OAuth2Application compatibility) Assisted-By: Claude Code
B-Whitt
force-pushed
the
django-50-upgrade
branch
from
06750d6 to
582544b
Compare
|
Contributor
Author
@ttuffin e2e failures fixed in this PR - https://github.com/ansible/eda-qa/pull/499. Resolve test failures caused by Django 5.x's stricter email TLD validation that no longer allows digits in top-level domains. eda-server e2e tests are passing with the eda-qa updates. See tests here |
hsong-rh
approved these changes
Dec 17, 2025
ttuffin
approved these changes
Dec 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Note: DRF remains at 3.15.x due to django-ansible-base constraint (requires DRF <3.16 for OAuth2Application compatibility)
Assisted-By: Claude Code