-
Notifications
You must be signed in to change notification settings - Fork 26
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
Newer version of oxidized-script gem #43
Comments
@ytti, can you give me permissions in the github project and on rubygems? then I will publish a new gem |
@mortzu you actually had it on rubygems, I removed them earlier today for three independent reasons, inactivity, another contributor rolled gem for oxidized yesterday and lack of MFA. I will give @aschaber1 right of first refusal, on thesis that more cooks isn't better for pushing out releases. Should he refuse, I'll set you up. |
yeah. thats fine for me |
I'm happy either way. I can do the release today, or @mortzu can do it. |
oxidized version 0.29 is now available |
any news? |
My friend created some pipelines which might help us out :) |
+1 on finishing this off - just did a new gem install and have ended up with:
Trying to debug that any further is really hard without hacking around in the code (-d and -v flags don't seem to have helped) and I don't want to do that on an old version if the new version is apparently working. |
we have the same problem. With oxidized 0.29.1 the connection works, with oxs or oxidized-script 0.6.0 no connection can be established. Same error as with cjwbath |
Up. |
Hi @ytti, do you have any plan to publish newer version as gem?
oxidized-script
0.6.0
doesn't work along with oxidized0.28
due to version conflict of "slop" gem.Thanks,
oxidized-script 0.6.0
oxidized-script/oxidized-script.gemspec
Lines 16 to 17 in a86cebb
oxidized 0.28.0
https://github.com/ytti/oxidized/blob/835384c6bb3a02896d05c73a1476c054b0856965/oxidized.gemspec#L27
The text was updated successfully, but these errors were encountered: