Not really.
From what I gather it is now limited to specifying Sender Name and has been stripped of the option to insert Sender emai with <> brackets as it was before the update.
So now all emails come from the main email and not from the aliases.
You are right, Looking at the code for the node we only set the name now as the email needs to be the same one that authenticates in the API so could lead to errors. We now automatically get the users email from the profile.
Were you previously using a different email address from the authenticated user? As a workaround if you take one of your old nodes from a previous workflow you can copy / paste it into a new workflow and you will be able to use the previous version.
I have added this to our internal feature request tracker so that we can evaluate adding it back in.