id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
36234	Restore single_object argument to LogEntry.objects.log_actions()	Adam Johnson		"#36217 / [https://github.com/django/django/pull/19214/files#diff-d146e5e5e0435a08eb6bf67f501b7b7dc4a28b3aa66caf47f48fe374d9732366L27-L29 this part of the PR] dropped the `single_argument` argument in a bug fix release, 5.1.7. Consequently, the method has two signatures in different Django 5.1 versions. I found real-world breakage from this in:

* a client project which had calls to `log_actions()`
* django-import-export - https://github.com/django-import-export/django-import-export/pull/2045
* django-stubs - https://github.com/typeddjango/django-stubs/blob/master/django-stubs/contrib/admin/models.pyi#L33 would need changing

I propose that we restore the argument in Django 5.1 and deprecate it from Django 5.2. It doesn’t make sense that we’d go through the deprecation pathway for the `log_action()` -> `log_actions()` migration, but drop an argument in a point release."	Bug	new	contrib.admin	5.1	Release blocker				Unreviewed	0	0	0	0	0	0