Skip to content

Releases: matthewwithanm/django-imagekit

V. 5.0

28 Sep 00:55
Compare
Choose a tag to compare

This is major version which will drop compatibility with old Python and Django versions.

Supported Python versions are: 3.7, 3.8, 3.9, 3.10, 3.11
Supported Django Versions are: 3.2, 4.1, 4.2

Upgrading since 4.x

Except from dropping support from older Python and Django versions there are no major changes in the API and most users will do not need to change anything in their code in order to upgrade from Django ImageKit 4.x to 5.x.

One minor thing that you can look for. If you are using Django 4.2+ and have more than one configured storage
using STORAGES you can now configure IMAGEKIT_DEFAULT_FILE_STORAGE to use the name defined in STORAGES
instead of dotted path to the storage class

Changes since 4.1.0

New Contributors

Full Changelog: 4.1.0...5.0

v. 4.1

17 Dec 07:00
Compare
Choose a tag to compare

This is feature release. Add support for new Python and Django versions.

  • Supported Python versions are: 2.7, 3.6, 3.7, 3.8, 3.9, 3.10
  • Supported Django versions are: 1.8, 1.11, 2.2, 3.1, 3.2

Upgrading since 4.0

Nothing special except to ensure that you are using supported Python and Django version

Changes since 4.0.2

Full changelog 4.0.2...4.1.0

Highlights

  • Add support for Django 2 and Django 3
  • Test against latest versions of Python (up to 3.10)
  • Stop testing for Django older than 1.8 and Python
  • Stop testing against Python 3.3 to 3.5
  • Change tests infrastructure (Use Github Actions instead of Travis CI and migrate to pytest instead of nose)
  • Add support for Celery 5 (#513)
  • Add new async backend - Dramatiq (trough django-dramatiq) (#527)
  • cachefile_storage now accepts callable (#525)
  • Documentation fixes
  • Fixes LazyImageCacheFile generating the wrong size image (#326)
  • Fixes pickle serialization to help S3 storage (#437, #451)

v4.0.2

20 Nov 09:30
Compare
Choose a tag to compare

It's a bugfix release. It includes:

  • Fix: do not leak open files
  • Fix ImageCacheFile.__repr__ to not send signals
  • Fix generateimages management command to work for Django 1.10+
  • Fix using specs directly in ProcessedImageField
  • Documentation fixes

v4.0.1

17 Jul 07:53
Compare
Choose a tag to compare

It's a bugfix release. It includes:

  • Fix performance regression for Django >= 1.7 in ImageKit 4.0 (#417)
  • Documentations fixes (#414, #415)

Full changelog 4.0...4.0.1

v. 4.0

02 Mar 18:45
Compare
Choose a tag to compare

This is major version which will drop compatibility with old Python and Django versions.

  • Supported Python versions are: 2.7, 3.3, 3.4, 3.5
  • Supported Django Versions are: 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10, 1.11

Upgrading from 3.x

Except from dropping support from older Python and Django versions there are no major changes in the API and most users will do not need to change anything in their code in order to upgrade from 3.x to 4.0. Still you can look down for Backward incompatible changes

Changes since 3.3

Full changelog 3.3...4.0

Highlights

  • Add support for Django 1.10 and 1.11
  • Move imagekit.templatetags.compat outside of imagekit.templatetags (Fixes #330, #331 and #352)
  • Include the test suite in the sourcetarball but do not install it. It can be used
    by distribution packages during build time (#363)
  • Various tests improvements:
    • Replace Lenna image in tests with a truly free alternative (#364)
    • Tests no longer leave junk (Fixes #382)
  • honor post_save's update_fields and only fire the source_saved signal when needed (#390)
  • Close the file only if it has been opened locally (Fixes #404)
  • autodiscover works with AppConfig (#412)
  • Add wheels support (#411)
  • Do not try south modelinspector when not needed (Fixes #408)
  • Improve caching (Fixes #399 #402)

Backward incompatible changes

Most of the changes probably will not affect you but still there are changes that can affect you:

  • If you import something from imagekit.templatetags.compat (it's internal API and you should not import anything from there) then you need to fix your imports because this module is now moved to imagekit.compat
  • If you have set IMAGEKIT_CACHE_BACKEND and rely on TIMEOUT defined there it will no longer use that value. Now by default in production (when DEBUG = False) timeout will be None which means forever. If you want to change this value you need to set IMAGEKIT_CACHE_TIMEOUT