I ran into the same issue as reported in #288 and realized its fix was dropped in v3.3.0.

It looks to me like the v3 branch never got merged into the main branch while development continued there.