v2.1.2 contains breaking changes.

[BlackGlory]

I don't have a clue about this, all my related test cases failed on 2.1.2.

In addition, v2.1.2 does not have a git tag, and 2.1.1 and 2.1.0 are also very confusing in the commits.

[octet-stream]

Hi! I think this may happen because of this: #85
You'll better stick with 2.1.1 until the next version is arrive...

[octet-stream]

I mean, this PR should fix the problem

[jimmywarting]

Do you know what is failing?
can you figure out what is breaking?

[BlackGlory]

Sorry, I don't have time to reply.

I tried the latest commit (a8fed4e) and it passed the test,
so I guess #85 fixed the problem. When will the new version be published?