Once again, thank you for bringing this to our attention @ajjulian!
This should now be fixed with 1.4.0.1:
Kindly let me know if this is the case on your end.
Thank you in advance.