Drf-tracking

Latest version: v1.5.0

Safety actively analyzes 665909 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 2

1.0.1

Not secure
- Fixes installation issue for Mysql backend support 29
- Updates TravisCI Tox testing to run against MySQL, PostgreSQL, & SQLite backends 29

NOTE: This version refactors drf-tracking's initial migration file and is likely backwards incompatible with current installations. Upgrade with caution.

Thanks to jameshiew

1.0.0

Not secure
This release addresses:
- Support for MySQL backend 19 , 25
- Refactored fields used on the `APIRequestLogAdmin` class 21
- Updates to docs and package metadata to align requirements for DRF, Django, & Python versions 30
- `PrefetchUserManager` class query performance enhancement 23

**NOTE:** This version refactors drf-tracking's initial migration file and is likely backwards incompatible with current installations. Upgrade with caution.

Thanks to ( jameshiew , zatarus , null-none , abriemme )

0.2.5

Not secure
APIRequestLog.remote_addr` is now X_FORWARDED_FOR by default, REMOTE_ADDR if not. This closes PR 14 and PR 15. Thanks yrchen!

0.2.4

Not secure
Add MySQL support, and refactor to not override DRF error message when user is inactive. Thanks mayankkapoor!

Page 2 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.