-
Notifications
You must be signed in to change notification settings - Fork 578
UN-3186 [FEAT] Add is_deprecated field to User model for OAuth email change handling #1763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
UN-3186 [FEAT] Add is_deprecated field to User model for OAuth email change handling #1763
Conversation
…change handling Co-Authored-By: Claude Opus 4.5 <[email protected]>
WalkthroughIntroduces a new indexed boolean field Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Test ResultsSummary
Runner Tests - Full Report
SDK1 Tests - Full Report
|
|



What
is_deprecatedboolean field to User modelWhy
How
is_deprecatedfield withdefault=Falseanddb_index=Truefor efficient filtering0003_user_is_deprecated.pyCan this PR break any existing features. If yes, please list possible items. If no, please explain why.
False, so all existing users remain activeDatabase Migrations
backend/account_v2/migrations/0003_user_is_deprecated.py- Addsis_deprecatedboolean fieldEnv Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
Notes on Testing
python manage.py migrate account_v2User.objects.filter(is_deprecated=False).exists()Screenshots
N/A
Checklist
I have read and understood the Contribution Guidelines.
🤖 Generated with Claude Code