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

Recent "yanking" of fastlane_core 0.60.0 causes dependency issue with watchbuild #1

Closed
lemonkey opened this issue Dec 21, 2016 · 2 comments

Comments

@lemonkey
Copy link

Bundler could not find compatible versions for gem "fastlane_core":
In Gemfile:
fastlane_core (= 1.0.0)

watchbuild (= 0.1.4) was resolved to 0.1.4, which depends on
  fastlane_core (< 1.0.0, >= 0.43.1)

My Gemfile currently has 0.1.4 defined as it's the latest version.

However, I'm currently being forced to point to fastlane_core 1.0.0 in my Gemfile since if I don't, it will try to find 0.60.0 which has recently been yanked from rubygems.org:

This version has been yanked, and it is not available for download directly or for other gems that may have depended on it.

VERSIONS:
1.0.0 - December 18, 2016 (44 KB)
0.59.0 - December 7, 2016 (43.5 KB)
0.58.0 - December 5, 2016 (43 KB)
0.57.2 - November 29, 2016 (43 KB)
0.57.1 - November 23, 2016 (43 KB)

@lemonkey
Copy link
Author

I could obviously remove watchbuild from the Gemfile but that's not ideal for my situation long term.

@milch
Copy link
Collaborator

milch commented Dec 22, 2016

Hi @lemonkey, I just released a new version of watchbuild (0.2.0) that should fix your error. Sorry about that!

I'm going to close this now, so just let me know if it's still not working for you after this and we'll reopen it!

@milch milch closed this as completed Dec 22, 2016
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

2 participants