Update ring

[matthauck]

No description provided.

[Keats]

It's not that simple sadly. There can only be a single version fo ring across someone project so we have to wait until a non-alpha release as otherwise every alpha release of ring would be a major version of jsonwebtoken as well

[matthauck]

Yeah, it was a ring-asm version conflict from upgrading ring in another project that led me to need to update it for jsonwebtoken too. Unfortunate that there is such a tight coupling. Hopefully ring-asm doesn’t change too frequently?

…

On Sat, Jul 14, 2018 at 12:03 AM Vincent Prouillet ***@***.***> wrote: It's not that simple sadly. There can only be a single version fo ring across someone project so we have to wait until a non-alpha release as otherwise every alpha release of ring would be a major version of jsonwebtoken as well — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#58 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABP3r6YBtmx4fdM_OTfQ3foyI4v55P6gks5uGZfHgaJpZM4VPmbX> .

[Keats]

Ring 0.13 was actually released Friday but briansmith/ring#619 is not in it and the repo Cargo.toml is still showing alpha.
A major version will require #57 to be done as well so I'll have a look next week