Skip to content

Releases: craigds/django-typed-models

0.14.0

24 Oct 22:11
Compare
Choose a tag to compare
  • Added support for Django 4.2 and 5.0.
  • Added support for Python 3.12.
  • Dropped the VERSION and __version__ attributes. To check the version of the package, use importlib.metadata.version("django-typed-models") (docs / backport).

0.13.0

14 Mar 23:35
Compare
Choose a tag to compare
Release 0.13

Add Django 4.x support

22 Aug 23:31
Compare
Choose a tag to compare
0.12.0

Bump version to 0.12.0

Bugfix release

13 Sep 21:04
Compare
Choose a tag to compare
  • Fixes an error using an abstract model as a superclass of typed proxy models (#61)

Django 3.1+ support; more explicit fields

19 Aug 22:57
Compare
Choose a tag to compare
  • Requires Django 3.1+, supports 3.1 or 3.2 (#59)
  • Fields can now be defined on multiple subclasses as long as the field definitions are identical (#48)
  • Two small backward-incompatible changes; see CHANGES.md

Python/django support update

27 Jul 20:59
Compare
Choose a tag to compare
  • Dropped Python 2 support
  • Added support for django 2.2 and 3.0, and dropped support for <2.2.

0.9.0

06 Jan 20:18
Compare
Choose a tag to compare
  • Improvements to explicit calls to recast() (#45)
  • Dropped shims for unsupported djangoes

0.8.0

27 Feb 19:25
Compare
Choose a tag to compare
  • Django 2.0 support (currently tested on 1.8, 1.10, 1.11, 2.0)
  • Removed implicit null=True. BACKWARDS INCOMPATIBLE: Please see CHANGES.md

0.7.0

02 Jun 21:17
Compare
Choose a tag to compare

Support for Django 1.11
Drop support for Django 1.9
Use pytest for tests
One small backwards incompatibility - see CHANGES.md

Django 1.10 support

15 Dec 02:09
Compare
Choose a tag to compare
  • Add support for django 1.10
  • Drop Django 1.7, since it's no longer supported upstream.
  • Fix choices for type field in django 1.9+ (#29)
  • Avoid check warnings for M2M fields (#28)