I'm not sure how that would have happened either, but the fix has been added for the next version. Thanks for the catch and the fix respectively!
