Thanks for letting me know, and thanks for picking it up!
This has been fixed in v1.1.0. Thanks again for reporting it!
