The release containing the fix is now available.
The community would like to thank maintainer @kahirokunn for reporting and fixing the issue.