Skip to content
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

Closed
MacksMind opened this issue Aug 31, 2015 · 6 comments
Closed

Pulling 4.0.2 caused breakage #53

MacksMind opened this issue Aug 31, 2015 · 6 comments

Comments

@MacksMind
Copy link

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?

@ioquatix
Copy link
Member

ioquatix commented Sep 1, 2015

Good idea.. @digitalextremist, can you sort this out?

@tarcieri
Copy link
Contributor

tarcieri commented Sep 1, 2015

A 4.0.3 seems like the simplest way out of this quagmire despite whatever philosophical implications about semantic versioning.

@digitalextremist
Copy link
Contributor

In a few hours I will cut 4.1.0 as 4.0.3 also, rather than 4.0.1 being 4.0.3

@digitalextremist
Copy link
Contributor

Actually, this will be 4.0.4 -- as a duplicate of 4.1.1

@digitalextremist
Copy link
Contributor

The gem is about to be cut once the tests pass.

@digitalextremist
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants