Catch up for ActiveWhatever 4.1.1 series about ruby-jwt HOT 6 CLOSED

I don't think they should be using 0.1.12 since it was released and yanked not long after. However, I'll see if I can release 0.1.11 as 0.1.12 to resolve this issue.

from ruby-jwt.

All I could find in my updated bundle was jwt (~> 0.1.8) for oAuth2 gem... wish it was clearer what gem was borking on needing 0.1.12 of jwt

from ruby-jwt.

Well I can't re-release a gem that was already released and yanked. So I
can't easily fix this. The problem is somewhere there is a Gemfile.lock
that is explicitly using 0.1.12

On Thu, May 8, 2014 at 1:32 PM, David Lazar [email protected]:

All I could find in my updated bundle was jwt (~> 0.1.8) for oAuth2 gem...
wish it was clearer what gem was borking on needing 0.1.12 of jwt

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/40#issuecomment-42587322
.

Jeff Lindsay
http://progrium.com

from ruby-jwt.

You could release 0.1.11 as 0.1.13 so those with 0.1.12 in Gemfile.lock's can bundle update and get a working version.

from ruby-jwt.

Good idea. That worked. Done.

from ruby-jwt.

@progrium Thanks Jeff. Problem solved.

from ruby-jwt.