This was a bug discovered in #108 . The fix for this has been pushed and tagged as a `v2.0.1` release