Releases: jazzband/django-simple-history
Releases · jazzband/django-simple-history
Release 2.11.0
Release 2.10.0
- Added
bulk_update_with_history
utility function (gh-650) - Add default user and default change reason to
bulk_create_with_history
andbulk_update_with_history
(gh-653) - Add french translation (gh-654)
- Start using
_change_reason
instead ofchangeReason
to add change reasons to historical
objects.changeReason
is deprecated and will be removed in version3.0.0
(gh-655)
Release 2.9.0
- Add simple filtering if provided a minutes argument in
clean_duplicate_history
(gh-606) - Add setting to convert
FileField
toCharField
instead ofTextField
(gh-625) - Added notes on BitBucket Pipelines (gh-627)
- import model
ContentType
inSimpleHistoryAdmin
usingdjango_apps.get_model
to avoid possibleAppRegistryNotReady
exception (gh-630) - Fix
utils.update_change_reason
when user specifies excluded_fields (gh-637) - Changed how
now
is imported fromtimezone
(timezone
module is imported now) (gh-643) - settings.SIMPLE_HISTORY_REVERT_DISABLED if True removes the Revert
button from the history form for all historical models (gh-632))
Release 2.8.0
- Fixed
bulk_create_with_history support
for HistoryRecords withrelation_name
attribute (gh-591) - Added support for
bulk_create_with_history
for databases different from PostgreSQL (gh-577) - Fixed
DoesNotExist
error when trying to get instance if object is deleted (gh-571) - Fix
model_to_dict
to detect changes in a parent model when using
inherit=True
(backwards-incompatible for users who were directly
using previous version) (gh-576) - Use an iterator for
clean_duplicate_history
(gh-604) - Add support for Python 3.8 and Django 3.0 (gh-610)
Release 2.7.3
Release 2.7.2
- Fixed ModuleNotFound issue for six (gh-553)
Release 2.7.1
Release 2.7.0
- * Add support for
using
chained manager method and save/delete keyword argument (gh-507) - Added management command
clean_duplicate_history
to remove duplicate history entries (gh-483) - Updated most_recent to work with excluded_fields (gh-477)
- Fixed bug that prevented self-referential foreign key from using
'self'
(gh-513) - Added ability to track custom user with explicit custom
history_user_id_field
(gh-511) - Don't resolve relationships for history objects (gh-479)
- Reorganization of docs (gh-510)
* NOTE: This change was not backward compatible for users using routers to write
history tables to a separate database from their base tables. This issue is fixed in
2.7.1.
Release 2.6.0
- Add
app
parameter to the constructor ofHistoricalRecords
(gh-486) - Add
custom_model_name
parameter to the constructor ofHistoricalRecords
(gh-451) - Fix header on history pages when custom site_header is used (gh-448)
- Modify
pre_create_historircal_record
to passhistory_instance
for ease of customization (gh-421) - Raise warning if HistoricalRecords(inherit=False) is in an abstract model (gh-341)
- Ensure custom arguments for fields are included in historical models' fields (gh-431)
- Add german translations (gh-484)
- Add
extra_context
parameter to history_form_view (gh-467) - Fixed bug that prevented
next_record
andprev_record
to work with custom manager names (gh-501)
Release 2.5.1
- Add '+' as the history_type for each instance in bulk_history_create (gh-449)
- Add support for history_change_reason for each instance in bulk_history_create (gh-449)
- Add history_change_reason in the history list view under the Change reason display name (gh-458)
- Fix bug that caused failures when using a custom user model (gh-459)