-
Notifications
You must be signed in to change notification settings - Fork 7
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
publish new version to rubygems #7
Comments
I upped the version in my fork to 0.15.5 and the rake tests ran without error. Wanna try building & publishing it again? |
Awesome thanks. I think that worked! I just pushed version 0.1.6, want to try that out and let me know if I did that right? It's been a while since I've pushed a gem! |
Looks like it went through. Will test it now. On a side note, it doesn’t look like the code for pingbacks is in here yet, is that right? |
oh funny, you're right. The only mention of pingback in the library is a commented out section marked as "TODO". Honestly I'd be happy if someone else took over maintaining this. I haven't used it myself in a while actually, since I switched to the PHP library and using https://telegraph.p3k.io for things. |
No worries. I was going to integrate pingback into my Jekyll plugin (as I think it’s a sensible feature request), but I could look at adding it here instead. Watch this space… |
Thanks @aaronpk. I've updated to 0.1.6 and no issues. |
Oh, and I'd be happy to help out with this gem. I use it for my personal site so I'm invested in ensuring it works well :) |
Adding this issue to the v1.0.0 milestone for tracking purposes. The underlying task might be to update the documentation with notes as to who currently has permissions to publish the gem to RubyGems.org (at the moment @aaronpk and I are owners). |
my first attempt at building and installing the update breaks because of an error with httparty versions. I'll need to investigate this further. Probably will need to update the library to work with a newer httparty version.
The text was updated successfully, but these errors were encountered: