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
36217	post_save signal is not called when LogEntry has Deletion action	smiling-watermelon	Antoliny	"I've added a post_save signal for my application to show LogEntry entities in my logs, but have ran into the following problem:
If I remove some object from admin, LogEntry with Deletion action is created and stored in the database, but my post_save signal is not called.

I've ensured that other actions are working fine:
- Addition
- Change

So, for some reason only ""Deletion"" action doesn't cause the `post_save` signal to be called.

To help reproduce the issue I've created a small [https://github.com/smiling-watermelon/logentry-bug-demo repository on GitHub] (basically following Django's documentation on creating a project), and added my signal there.

If you need any more info from me, just let me know, hopefully the README is pretty easy to follow and understand.

The exact Django version I've been using is 5.1.6, in both - the demo (though there it's not pinned!) and my real project."	Bug	closed	contrib.admin	5.1	Release blocker	fixed	LogEntry Signals post_save	smiling-watermelon Akash Kumar Sen David Wobrock Nick Pope Mariusz Felisiak	Ready for checkin	1	0	0	0	0	0