# What changed in django-guid

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

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

## django-guid 3

### Breaking changes

- Requires Django 3.1.1 or later; earlier Django versions should use django-guid<3.0.0. (3.0.0) — [release notes](https://github.com/snok/django-guid/releases/tag/3.0.0)

### New APIs and options

- Adds full async/ASGI support alongside the existing WSGI support. (3.0.0) — [release notes](https://github.com/snok/django-guid/releases/tag/3.0.0)

### Fixes and other changes

- Adds support for Django 6.0. (3.6.0) — [release notes](https://github.com/snok/django-guid/releases/tag/3.6.1), [release notes](https://github.com/snok/django-guid/releases/tag/3.6.0)

## django-guid 2

### Breaking changes

- django_guid must be listed in INSTALLED_APPS due to its usage of signals. (2.0.0) — [release notes](https://github.com/snok/django-guid/releases/tag/2.0.0)

### Deprecations

- SKIP_CLEANUP is deprecated; after a request finishes, the Correlation ID is cleaned up using the request_finished Django signal. (2.0.0) — [release notes](https://github.com/snok/django-guid/releases/tag/2.0.0)