I’m closing that PR because I can’t reproduce the issue and nobody else reported a similar issue.
Migration::ColumnDropper.execute_drop drops the read_only function for each column with CASCADE. That also drops the trigger.
It sounds like you had a trigger that didn’t reference the read_only function. I’m not sure how you managed to do this. Are you using a standard install?