Django-imagefield

~~~~~~~~~~~~~~~~~

- **Important:** Changed the image field to no longer automatically clean up
processed images when deleting the model instance or when changing the image
field itself. This behavior made it hard to reuse image field values when
copying model data. Instead, processed images are only deleted when the image
file itself is deleted (e.g. using ``object.image.delete()``).
- Rewrote ``process_imagefields`` to use the multiprocessing module, which
hopefully improves compatibility on macOS.
- Introduced a ``--no-parallel`` argument to ``process_imagefields``.
- Added Django 5.2a1.
- Dropped the Python 2 fallback from the code. We don't support Python 2
anymore.

~~~~~~~~~~~~~~~~~

- Documented the ``preview`` spec used in the preview widget.
- Started masquerading our custom model fields as default Django image and char
fields. This is expected to create migrations if you're already using the
fields.

~~~~~~~~~~~~~~~~~

- Added support for setting ``IMAGEFIELD_AUTOGENERATE = False``. Previously,
only ``True`` or an iterable were supported.
- Dropped compatibility with Python 3.8 and 3.9.
- Added Python 3.13.
- Excluded Pillow 11.0.0 from the list of supported Pillow versions, see
`8535 <https://github.com/python-pillow/Pillow/issues/8530>`__.

~~~~~~~~~~~~~~~~~

- Updated the pre-commit configuration, switched to biomejs.
- Started using a process pool to process images in parallel in
``process_imagefields``.
- Added Django 5.1rc1 to the CI, removed 4.1 (3.2 is still there).
- Attached signal handlers to model subclasses as well, so that proxy models
are supported too.

~~~~~~~~~~~~~~~~~

- Added Python 3.12, Django 5.0.
- Added an easy way to reduce the possibility of filename collisions.
Unfortunately, the hashing scheme used by default has bad uniqueness
properties. It's recommended to add ``IMAGEFIELD_BIN_DEPTH = 2`` to your
settings and regenerate all processed images, for example using
``process_imagefields --all``. The default may change in the future. For now
nothing changes, so there's no compatibility concerns.

~~~~~~~~~~~~~~~~~

- Added a force-WEBP spec.
- Added Django 4.1 and 4.2, Python 3.11.
- Dropped Django 4.0 from the CI (3.2 is still in there).
- Switched to hatch and ruff.
- Added globbing support to the ``process_imagefields`` management command.