Hi @Marius,
Thank you for bringing this to our attention!
This should now be fixed with 1.4.0.1, with the addition of a notice:
Kindly let me know if this is the case on your end.
Thank you in advance.