v0.5.3 is a breaking change

[ivolucien]

v0.5.1...v0.5.3#diff-e41c65498b26286ad5bf2a9f21ff0722R79

This above code changes the default encoding that breaks callers who depend on the old handling.

In our case the header specifies an encoding that is not RS256 which the new code ignores.

I suggest that you rev the minor version, with an explanation of the change in the README.md

That at least will spare folks the research into why decoding is broken (for that subset of users.)

Thank you much

[ivolucien]

I realize that semver would dictate the major version be rev'd for non-backwards compatible changes, but I can imagine you might not want to release v1.0.0 with only that announcement.