-
Notifications
You must be signed in to change notification settings - Fork 18
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
New release? #10
Comments
I'll check this out. |
@jaredmdobson : if possible, I'd like to be added to the maintainers of the project :-) I could handle pushing to rubygems I don't want to be the new owner of the project though - unless you really don't want to be the owner anymore. Thx! |
@Kulgar i added you and i can add your email to our rubygem project. |
@jaredmdobson yes please, add my email to the rubygem project :-) I'll gladly push the new releases, thx!! |
Done :) |
It appears that the rubygem points to your fork now.
However the rubygem is currently showing
0.3.17
as the latest version. Your repo shows the latest tag as0.3.17
. However your code shows a0.4.2
.Would you be able to push 0.4.2 to rubygems?
(Figured this out via guard/guard-livereload#143 (comment))
The text was updated successfully, but these errors were encountered: