Skip to content

Django/Python version upgrades#44

Merged
snopoke merged 5 commits intomainfrom
sk/django-upgrades
Mar 4, 2026
Merged

Django/Python version upgrades#44
snopoke merged 5 commits intomainfrom
sk/django-upgrades

Conversation

@snopoke
Copy link
Copy Markdown
Contributor

@snopoke snopoke commented Mar 3, 2026

Summary

  • Drop Django 3.2 and Python 3.9 support (both EOL)
  • Add Django 5.2 to the stable CI matrix
  • Add Python 3.13 and 3.14 to the stable CI matrix
  • Replace experimental Django 5.0.x job with django==6.0.* on Python 3.12
  • Use CheckConstraint.condition on Django 5.1+ and check on older versions for cross-version compatibility

Test plan

  • CI passes on Django 4.2 and 5.2 across Python 3.10–3.13
  • Django 5.2 + Python 3.14 job passes
  • Experimental Django 6.0 job runs (failures are non-blocking)
  • Migration check step passes

🤖 Generated with Claude Code

snopoke and others added 5 commits March 3, 2026 10:55
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Use 'condition' kwarg on Django 5.1+ and 'check' on older versions,
since 'condition' was added in 5.1 and 'check' is removed in 6.0.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@snopoke snopoke changed the title Django 5.2 / 6.0 compatibility upgrades Django/Python version upgrades Mar 3, 2026
@snopoke snopoke requested review from SmittieC and gherceg March 3, 2026 10:10
@snopoke snopoke merged commit 016650a into main Mar 4, 2026
11 checks passed
@snopoke snopoke deleted the sk/django-upgrades branch March 4, 2026 06:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants