Closed tknzk closed 3 years ago
Was just about to open an issue myself. I only see this issue in v0.2.14
. I had to downgrade to v0.2.13
to get it to work again.
This should be fixed via 0.2.15
I'm sorry, it happened after my changes, I didn't notice this line and it didn't affect CI.
I've created #123 with a try to prevent such errors in future in one of commits.