Safety vulnerability ID: 42977
The information on this page was manually curated by our Cybersecurity Intelligence Team.
Django-idempotency-key 1.1.0 drops support for Django 1.x as it arrived to end of life.
Latest version: 1.2.0
Django middleware for idempotency key support in view and viewset functions.
**[Security updates]**
**[Dropped support]**
**[Added support]**
**[New features]**
**[Breaking changes]**
- The following classes have moved to a new namespace and need to be changed in your
settings and code where appropriate.
<pre>
idempotency_key.locks.IdempotencyKeyLock -> <strong>idempotency_key.locks.basic.IdempotencyKeyLock</strong>
idempotency_key.locks.ThreadLock -> <strong>idempotency_key.locks.basic.ThreadLock</strong>
idempotency_key.locks.MultiProcessRedisLock -> <strong>idempotency_key.locks.redis.MultiProcessRedisLock</strong>
</pre>
- Drop support for Django (1.9, 1.10, 1.11)
- 1.11 was dropped because of security issues and is near to end of life support.
- Added support for Django (2.2)
- Added testing with django rest framework (3.10, 3.11)
- Added optional flag so that clients can choose to use idempotency keys on an API that
is used to expect it.
- Updated packages with security issues:
Django (>=2.x)
bleach (>=3.1.4)
urllib3 (>=1.24.2)
---
Scan your Python project for dependency vulnerabilities in two minutes
Scan your application