Closed ys closed 10 years ago
Thanks Yannick!
I’ll :ship: a point release that includes this update.
Thanks to you:) I was looking at updating to the latest and this was the only issue
Hi, now thread_safe version becomes 0.3.0
, and ~>0.2.0
notation prevent to update the gem.
( https://github.com/headius/thread_safe/releases )
The change may not break this gem. ( https://github.com/headius/thread_safe/compare/0.2.0...0.3.0 )
So, why don't you change dependency notation to ~> 0.1
or >= 0.1.3
?
I just released memoizable 0.4.2
which upgrades to the latest thread_safe
https://rubygems.org/gems/memoizable/versions/0.4.2
@awakia I generally will always reference the latest stable version of a dependency because I don't want to deal with the combinatorial explosions of ruby versions × dependency versions. In some rare cases I will bend this rule, but not without a valid reason; by default I'll always bump to the latest dependency at the time of release.
@dkubb Thank you very much for quick updating! The change you did seems perfect choice for me!!
Updating to the latest version.
Using it with Rails 4.0.3 brings conflicts