yanking of version 0.1.12 causes issues about ruby-jwt HOT 4 CLOSED

Upgrade to 1.0.0 or explicitly use 0.1.11. Sorry for the mishap.

On Wed, May 7, 2014 at 2:45 PM, GhostGambler [email protected]:

http://stackoverflow.com/questions/23526673/cannot-push-to-heroku-bundler-fails

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/39
.

Jeff Lindsay
http://progrium.com

from ruby-jwt.

I have no influence on third party projects (besides opening tickets...)

For example oauth2 is affected:
https://github.com/intridea/oauth2/blob/master/oauth2.gemspec#L8

Isn't there another way to fix this problem?

from ruby-jwt.

Their gemspec is not requiring 0.1.12 so it's not an issue with third party
projects unless they explicitly depend on 0.1.12... instead wherever bundle
install was ran it has a cached copy of 0.1.12 that needs to be removed so
it can properly look up the latest version to grab similar to 0.1.8 which I
imagine resolves to 0.1.11

On Wed, May 7, 2014 at 4:04 PM, GhostGambler [email protected]:

I have no influence on third party projects (besides opening tickets...)

For example oauth2 is affected:
https://github.com/intridea/oauth2/blob/master/oauth2.gemspec#L8

Isn't there another way to fix this problem?

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

Jeff Lindsay
http://progrium.com

from ruby-jwt.

For what it's worth I have oauth-xx/oauth2#172 open which would resolve this.

In the meantime I've added this to our Gemfile to work around similar issues:

gem 'jwt', '~> 0.1.11'

from ruby-jwt.