GitHub / jazzband/django-fernet-encrypted-fields issues and pull requests
#26 - [pre-commit.ci] pre-commit autoupdate
Pull Request -
State: closed - Opened by pre-commit-ci[bot] 2 months ago
#25 - Fix version and typo
Pull Request -
State: closed - Opened by frgmt 5 months ago
#24 - Added ability to use Django's SECRET_KEY_FALLBACKS to rotate secret key
Pull Request -
State: closed - Opened by flaiming 5 months ago
- 3 comments
#23 - [pre-commit.ci] pre-commit autoupdate
Pull Request -
State: closed - Opened by pre-commit-ci[bot] 7 months ago
#22 - Fix to use ruff and fix some
Pull Request -
State: closed - Opened by frgmt 7 months ago
#21 - Encrypted fields should not assume None is an allowed value
Pull Request -
State: closed - Opened by scottpashley 9 months ago
#20 - Is there a guideline to migrate from obsoleta django-encrypted-fields?
Issue -
State: open - Opened by domdinicola about 1 year ago
- 2 comments
#19 - Improve CI setup, add testing with Django 5 and Python 3.11
Pull Request -
State: closed - Opened by artursmet over 1 year ago
- 1 comment
#18 - Update ci and code
Pull Request -
State: open - Opened by sevdog over 1 year ago
- 4 comments
#17 - Implement Jazzband guidelines for django-fernet-encrypted-fields
Issue -
State: open - Opened by jazzband-bot almost 2 years ago
- 2 comments
#16 - Adding typings to codebase
Issue -
State: open - Opened by faradayyg about 2 years ago
- 6 comments
#15 - Fix minimum django version to 3.2
Pull Request -
State: closed - Opened by frgmt about 2 years ago
#14 - Add support for encrypted JSON fields
Pull Request -
State: closed - Opened by faradayyg about 2 years ago
- 1 comment
#13 - Updating Django's SECRET_KEY makes encrypted fields inaccessible
Issue -
State: closed - Opened by hendrikschneider over 2 years ago
- 12 comments