Apologies for this oversight. I believe the issue has now been resolved and version 2.6.1 should work as expected.