# What changed in django-notifications-community

> 12 changes in django-notifications-community 1 from its official release notes, upgrade guides and advisories: 2 breaking, 5 new APIs and options. Each one cited. Sources checked 2026-10-25. HTML: https://unstale.sh/pypi/django-notifications-community/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## django-notifications-community 1

### Breaking changes

- JSON endpoint serialization now follows the notification model, skips many-to-many fields, and reduces file fields to their stored paths. (1.12.2) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.2)
- Django 4.2 and 5.1 are no longer supported; pin django-notifications-community<1.12 if you still need them. (1.12.0) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.0)

### New APIs and options

- Add this setting in DJANGO_NOTIFICATIONS_CONFIG to list model fields excluded from the JSON endpoints. (1.12.2) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.2)
- A registry hook lets companion packages plug into the queryset flow without forking views, helpers, or template tags. (1.12.0) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.0)
- A registry hook lets companion packages plug into the cache-key flow without forking views, helpers, or template tags. (1.12.0) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.0)
- A registry hook lets companion packages plug into the cache-key flow without forking views, helpers, or template tags. (1.12.0) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.0)
- The new optional sites extra installs django-notifications-community-sites, which scopes notifications to the current site via the registry hooks. (1.12.0) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.0)

### Performance

- ContentType lookups for the actor and optional target/action_object are resolved once per call instead of once per recipient. (1.12.1) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.1)

### Behavior and default changes

- 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. (1.12.0) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.0)

### Fixes and other changes

- 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. (1.12.2) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.2)
- Explicit data= payloads now survive and merge with extra kwargs instead of being replaced with an empty dict. (1.12.1) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.1)
- Passing timestamp=None now coerces it to timezone.now() instead of raising IntegrityError. (1.12.1) — [release notes](https://github.com/django-notifications-community/django-notifications-community/releases/tag/v1.12.1)