You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw that someone pushed a new version of rbtree (v0.4.4) on January 1, 2021.
Was it you? If so, how did you get access/rights to push the gem under the name rbtree?
Three years ago I made a fork of rbtree and released it as rbtree3 because I couldn't just push to rbtree.
I still maintain it but I am not sure who uses that besides me. It also includes some of the fixes you did here. Not sure if you saw my fork or https://github.com/skade/rbtree, where I was able to obtain the source code. @skadelet me know that he also doesn't have access to the rbtree gem on RubyGems.
The text was updated successfully, but these errors were encountered:
Hi there @zzak!
I saw that someone pushed a new version of rbtree (v0.4.4) on January 1, 2021.
Was it you? If so, how did you get access/rights to push the gem under the name
rbtree
?The owner of the gem is this profile: https://rubygems.org/profiles/lvfl98xod5hkd1mczt9yiuyoulblcy5z
Which, I believe, belongs to Ozawa Takuma.
Three years ago I made a fork of rbtree and released it as rbtree3 because I couldn't just push to
rbtree
.I still maintain it but I am not sure who uses that besides me. It also includes some of the fixes you did here. Not sure if you saw my fork or https://github.com/skade/rbtree, where I was able to obtain the source code. @skade let me know that he also doesn't have access to the
rbtree
gem on RubyGems.The text was updated successfully, but these errors were encountered: