I found the issue. I put the fix in the wrong file, so it was never included in the release. It'll be fixed in the next version.
