Yes, that was indeed a bug. Thank you for bringing it to my attention, it should be squashed now with hotfix v.0.1.2!
