chore(deps): Upgrade django-axes from 5.9.0 to 8.0.0

[webjunkie]

Summary

• Upgrades django-axes from 5.9.0 to 8.0.0 for Django 5 compatibility
• Applies 3 new migrations (0007, 0008, 0009)
• Fixes deprecated setting warning

Changes

1. Upgraded django-axes to 8.0.0

   • Supports Django 4.2, 5.1, 5.2 and Python 3.9-3.13
   • Required for subsequent Django 5 upgrade

2. Applied 3 new migrations

   • 0007_alter_accessattempt_unique_together - Deduplicates attempts and adds unique constraint
   • 0008_accessfailurelog - Creates new AccessFailureLog model
   • 0009_add_session_hash - Adds session_hash field to AccessLog
   • Note: We use AxesCacheHandler, so these tables won't be actively used

3. Fixed deprecated setting

   • Renamed AXES_META_PRECEDENCE_ORDER → AXES_IPWARE_META_PRECEDENCE_ORDER

4. Improved migration risk analyzer

   • Added POSTHOG_OWNED_APPS and is_posthog_app() helper
   • PostHog policies (UUID PKs, single migration) now only enforced on posthog/ee/products apps
   • Third-party dependency migrations can use their own conventions

Migration Risk

Low - Migrations are safe:

• ✅ 0009: Adds nullable field with default (safe)
• ⚠️ 0007: RunPython dedupe + unique constraint (low risk, small table)
• ✅ 0008: Creates new table (safe)

Test plan

• Migrations applied successfully locally
• Migration risk analyzer passes
• CI tests pass

[greptile-apps]

_{5 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[github-actions]

🔍 Migration Risk Analysis

We've analyzed your migrations for potential risks.

Summary: 2 Safe | 1 Needs Review | 0 Blocked

Legend: ✅ Safe = No locks, backwards compatible | ⚠️ Needs Review = May have performance impact | ❌ Blocked = Causes locks or breaks compatibility

⚠️ Needs Review

axes.0007_alter_accessattempt_unique_together
  └─ #1 ⚠️ RunPython: RunPython data migration needs review for performance
  └─ #2 ⚠️ AlterUniqueTogether: Altering unique constraints may lock table

✅ Safe

axes.0008_accessfailurelog
  └─ #1 ✅ CreateModel
     Creating new table is safe
     model: AccessFailureLog

axes.0009_add_session_hash
  └─ #1 ✅ AddField
     Adding NOT NULL field with constant default (safe in PG11+)
     model: accesslog, field: session_hash

📚 How to Deploy These Changes Safely

RunPython:

Large-scale considerations for data migrations:

• Use .iterator() for large querysets to avoid loading all rows into memory
• Process in batches: for obj in Model.objects.all().iterator(chunk_size=1000)
• Use .bulk_update() instead of saving individual objects
• Add progress logging every N rows for visibility
• Test on production-sized data before deploying
• Consider timeout limits - migrations blocking deployment for >10min are problematic