Update dependency django-simple-history to v3.7.0
This MR contains the following updates:
Package | Update | Change |
---|---|---|
django-simple-history (changelog) | minor |
==3.5.0 -> ==3.7.0
|
Release Notes
jazzband/django-simple-history (django-simple-history)
v3.7.0
- Dropped support for Django 3.2, which reached end-of-life on 2024-04-01 (gh-1344)
- Removed the temporary requirement on
asgiref>=3.6
added in 3.5.0, now that the minimum required Django version is 4.2 (gh-1344) - Migrated package building from using the deprecated
setup.py
to usingpyproject.toml
(with Hatchling as build backend);setup.py
has consequently been removed (gh-1348) - Added
django>=4.2
as an installation dependency, to mirror the minimum version tested in our CI (gh-1349)
v3.6.0
- Support custom History
Manager
andQuerySet
classes (gh-1280) - Renamed the (previously internal) admin template
simple_history/_object_history_list.html
tosimple_history/object_history_list.html
, and added the fieldSimpleHistoryAdmin.object_history_list_template
for overriding it (gh-1128) - Deprecated the undocumented template tag
simple_history_admin_list.display_list()
; it will be removed in version 3.8 (gh-1128) - Added
SimpleHistoryAdmin.get_history_queryset()
for overriding whichQuerySet
is used to list the historical records (gh-1128) - Added
SimpleHistoryAdmin.get_history_list_display()
which returnshistory_list_display
by default, and made the latter into an actual field (gh-1128) -
ModelDelta
andModelChange
(insimple_history.models
) are now immutable dataclasses; their signatures remain unchanged (gh-1128) -
ModelDelta
'schanges
andchanged_fields
are now sorted alphabetically by field name. Also, ifModelChange
is for an M2M field, itsold
andnew
lists are sorted by the related object. This should help prevent flaky tests. (gh-1128) -
diff_against()
has a new keyword argument,foreign_keys_are_objs
; see usage in the docs under "History Diffing" (gh-1128) - Added a "Changes" column to
SimpleHistoryAdmin
's object history table, listing the changes between each historical record of the object; see the docs under "Customizing the History Admin Templates" for overriding its template context (gh-1128) - Fixed the setting
SIMPLE_HISTORY_ENABLED = False
not preventing M2M historical records from being created (gh-1328) - For history-tracked M2M fields, adding M2M objects (using
add()
orset()
) used to cause a number of database queries that scaled linearly with the number of objects; this has been fixed to now be a constant number of queries (gh-1333)
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.
Edited by Renovate Bot