-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Pulling 4.0.2 caused breakage #53
Comments
Good idea.. @digitalextremist, can you sort this out? |
A 4.0.3 seems like the simplest way out of this quagmire despite whatever philosophical implications about semantic versioning. |
In a few hours I will cut |
Actually, this will be |
The gem is about to be cut once the tests pass. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Moving 4.0.2 to 4.1.0 caused
bundle install
breakage for anyone unlucky enough to implement Sidekiq while 4.0.2 existed, because celluloid 0.16.1 lists timers ~> 4.0.0 as a dependency. Undoubtedly there are other use cases as well.Hand editing Gemfile.lock is a workaround, but maybe re-release 4.0.1 as 4.0.3 to provide an obvious resolution?
The text was updated successfully, but these errors were encountered: