Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release a new version #47

Closed
toshe opened this issue Nov 2, 2014 · 19 comments
Closed

Release a new version #47

toshe opened this issue Nov 2, 2014 · 19 comments

Comments

@toshe
Copy link

toshe commented Nov 2, 2014

Can you please release a new version? The latest version in the gem repository does not include the exp claim implementation which is really practical. :)

@cthornton
Copy link

👍

@Lordnibbler
Copy link

Yes please do this! 👍

@Lordnibbler
Copy link

It's actually impossible to point to HEAD on github, since you depend on Echoe to create your gemspec.

@jimberlage
Copy link

👍

@Lordnibbler
Copy link

😢 😞 please?

@edowling
Copy link

👍

@drhurd
Copy link

drhurd commented Nov 13, 2014

This would be super helpful!

@yolk
Copy link

yolk commented Nov 17, 2014

  • 1

Anything I/we could do to help get the new version released?

@progrium
Copy link
Contributor

Hmm... where did @sporkmonger go? Anybody else want to help co-maintain and push releases?

@sporkmonger
Copy link
Contributor

I still exist, but with less free time due to startup that doesn't use this gem. :-/

I'd recommend nominating @sqrrrl here because Google has a vested interest in this gem.

@progrium
Copy link
Contributor

If @sqrrrl is interested, otherwise anybody else?

@yolk
Copy link

yolk commented Nov 21, 2014

I could do some housekeeping. But I'm a stranger to all of you and wasn't involved in the project till know. I have a general interest in JWT and a stable and conform implementation for ruby, that's all ;)

@jimberlage
Copy link

My situation is pretty much the same as @yolk.

@Lordnibbler
Copy link

Come on guys how hard is it to release a new version.

Sent from my iPhone

On Nov 24, 2014, at 7:26 AM, jamesberlage [email protected] wrote:

My situation is pretty much the same as @yolk.


Reply to this email directly or view it on GitHub.

@progrium
Copy link
Contributor

Released 1.2.0 ... it's not hard, but it's a great forcing function to
solve the problem long term. Ideally it were automated with PRs to a
release branch. I just don't have time.

On Mon, Nov 24, 2014 at 9:35 AM, Ben [email protected] wrote:

Come on guys how hard is it to release a new version.

Sent from my iPhone

On Nov 24, 2014, at 7:26 AM, jamesberlage [email protected]
wrote:

My situation is pretty much the same as @yolk.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub
#47 (comment).

Jeff Lindsay
http://progrium.com

@takashi
Copy link

takashi commented Dec 22, 2014

@progrium 👍 for release 1.2 and can you add .gemspec to this project? it will help us to track master branch of this gem

@xpepermint
Copy link

+1

@excpt
Copy link
Member

excpt commented Jan 23, 2015

New version 1.2.1 released.

@excpt excpt closed this as completed Jan 23, 2015
@takashi
Copy link

takashi commented Jan 24, 2015

🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests