Probably 0.1.6, we just updated to 0.1.7, yay
Thanks for the comment. We haven't been able to replicate the bug just yet, but it's noted :)
