-
Notifications
You must be signed in to change notification settings - Fork 376
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
Comments
👍 |
Yes please do this! 👍 |
It's actually impossible to point to HEAD on github, since you depend on Echoe to create your gemspec. |
👍 |
😢 😞 please? |
👍 |
This would be super helpful! |
Anything I/we could do to help get the new version released? |
Hmm... where did @sporkmonger go? Anybody else want to help co-maintain and push releases? |
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. |
If @sqrrrl is interested, otherwise anybody else? |
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 ;) |
My situation is pretty much the same as @yolk. |
Come on guys how hard is it to release a new version. Sent from my iPhone
|
Released 1.2.0 ... it's not hard, but it's a great forcing function to On Mon, Nov 24, 2014 at 9:35 AM, Ben [email protected] wrote:
Jeff Lindsay |
@progrium 👍 for release 1.2 and can you add .gemspec to this project? it will help us to track master branch of this gem |
+1 |
New version 1.2.1 released. |
🎉 |
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. :)The text was updated successfully, but these errors were encountered: