@ James
I’ve identified the bug and will be leasing a bug release, version 0.8.7, which will fix this this issue. Apologies for the trouble!
