Confirmed. Obviously it was working before. [~firstname.lastname@example.org], could this have anything to do with new role editing changes?
Update: It is failing because new drafts now have version = -1. The updateRoleAction() tries to load a draft where version = roleId, this doesn't exist yet. We could add an OR clause to the select, to support both cases:
( version = roleId OR (version = -1 AND role_id = roleId) )
Nevermind, I have a better solution, PR coming soon.