pypi / django-notifications-community
django-notifications-community
What changed in django-notifications-community 1, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-25.
2 breaking5 new APIs and options1 performance1 behavior and defaults3 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli initdjango-notifications-community 112 changes
Breaking changes 2
JSON endpoint serialization now follows the notification model, skips many-to-many fields, and reduces file fields to their stored paths.
Django 4.2 and 5.1 are no longer supported; pin django-notifications-community<1.12 if you still need them.
New APIs and options 5
Add this setting in DJANGO_NOTIFICATIONS_CONFIG to list model fields excluded from the JSON endpoints.
A registry hook lets companion packages plug into the queryset flow without forking views, helpers, or template tags.
A registry hook lets companion packages plug into the cache-key flow without forking views, helpers, or template tags.
A registry hook lets companion packages plug into the cache-key flow without forking views, helpers, or template tags.
The new optional sites extra installs django-notifications-community-sites, which scopes notifications to the current site via the registry hooks.
Performance 1
ContentType lookups for the actor and optional target/action_object are resolved once per call instead of once per recipient.
Behavior and default changes 1
The Django upper bound is relaxed to <6.3, allowing Django 6.0, 6.1, and upcoming 6.2 LTS to install without a release.
Fixes and other changes 3
Kwargs naming model fields are assigned to those fields, including foreign keys supplied as an instance or raw primary key, without depending on USE_JSONFIELD.
Explicit data= payloads now survive and merge with extra kwargs instead of being replaced with an empty dict.
Passing timestamp=None now coerces it to timezone.now() instead of raising IntegrityError.