Django-dirtyfields

------------------

*Bugfix:*
- Fixed a :code:`KeyError` that would occur when updating a field two times in a row when
the field value is set to an :code:`F` object and the field is specified in the
:code:`update_fields` argument to :code:`save()`. (209)

------------------

*New:*
- Confirm support for Python 3.11
- Confirm support for Django 4.1
- Drop support for Django 1.11

*Changed:*
- The method :code:`get_dirty_fields()` now returns only the file name for FileFields.
This is to improve performance, since the entire :code:`FieldFile` object will no longer
be copied when Model instances are initialized and saved. (203)

*Bugfix:*
- The method :code:`save_dirty_fields()` can now be called on Model instances that have not been
saved to the Database yet. In this case all fields will be considered dirty, and all will be
saved to the Database. Previously doing this would result in an Exception being raised. (200)

------------------

*Documentation:*
- General improvements to content and generation of Documentation (197).

------------------

*Documentation:*
- Document limitations when using dirtyfields and database transactions (148).
- Document how to use a Proxy Model to avoid performance impact (132).

------------------

*New:*
- Confirm support of Python 3.10
- Confirm support of Django 4.0
- Drop support for Python 3.6

*Tests*
- Run CI tests on Github Actions since travis-ci.org has been shutdown.

------------------

*New:*
- Provide programmatically accessible package version number. Use :code:`dirtyfields.__version__` for a string,
:code:`dirtyfields.VERSION` for a tuple.
- Build and publish a wheel to PyPI.

*Changed:*
- Only look at concrete fields when determining dirty fields.
- Migrate package metadata from setup.py to setup.cfg and specify the PEP-517 build-backend to use with the project.

*Bugfix:*
- Fixed a :code:`KeyError` that happened when saving a Model with :code:`update_fields` specified after updating a
field value with an :code:`F` object (118).