Is it necessary to dependency activesupport <5
I use cocoapods in rails 5.1 project , bundle install error
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
cocoapods (~> 1.3.1) was resolved to 1.3.1, which depends on
activesupport (< 5, >= 4.0.2)
rails (~> 5.1.0) was resolved to 5.1.0, which depends on
activesupport (= 5.1.0)
CocoaPods supports Ruby 2.0, which activesupport > 5 does not I'm afraid.
@orta any thoughts on dropping support for Ruby 2.0 now that Mojave is out and we have a full cycle of Mac OS releases with Ruby 2.3+ support? 🤠
We're keen to add support to automatically update Podfiles in Dependabot which uses Rails 5.
Original comment raising this: https://github.com/CocoaPods/CocoaPods/pull/5602#issuecomment-303251393
@feelepxyz do you have a link or other info which specifies which version of Ruby is included with each version of macOS?
@amorde I can't seem to find any official info but found the following reports:
10.12 Sierra ships with Ruby 2.0
10.13 High Sierra ships with Ruby 2.3.3
10.14 Mojave ships with Ruby 2.3.7
I don't think Apple officially announce this anywhere; another citation for Ruby version (that agree with what @feelepxyz said) is https://apple.stackexchange.com/questions/257627/ruby-version-on-macos-sierra
I believe CocoaPods has historically supported back 2 versions of macOS - @orta @segiddins does that sound right?
That sounds right? Also cc @DanToml
Edit: or maybe it was we support 2 versions of Xcode?
I feel like it was both Xcode and macOS
I don't think this is documented anywhere, and so I wouldn't be opposed to re-evaluating it. But would need to investigate the impact of dropping support for 2.0.0 - my guess is that a significant amount of users are still using 2.0.0 but I could be wrong
How about rolling this out? Show warning to user if pod
is called with Ruby 2.0?
Apple have been releasing new OS every year since Mac OS X Lion (10.7). With the “latest + 2 old” principle, we will be dropping 2.0 next fall anyway. If we are ever showing the deprecation warning, it’s time.
We can still support 2.0.0 (and we must until CocoaPods 2.0), but we can probably stop bending over backwards to make its experience as good as possible. So I’m fine just making the activesupport dependency >4,<6 personally.
@segiddins Any progress? If I understand correctly, the current plan is to write code compatible with both ActiveSupport 4.x and 5.x?
And shall we re-open this issue if this is the plan?
macOS High Sierra (10.13) comes with Ruby 2.3. Now that Catalina is released, Apple isn’t expected to support Sierra (10.12) any more. Is there any plan to upgrade ActiveSupport? Or at least, any plan to deprecate Ruby 2.1 or below?
Is this still an issue? I'd love to be able to use Dependabot with CocoaPods!
Yes, we are currently in a beta period for 1.9 so this likely won't change until after 1.9 is released
Just to officialize the conclusion of this issue, cocoapods dependency activesupport is > 5.0 && < 6.0
https://github.com/CocoaPods/CocoaPods/blob/master/Gemfile#L41 already (since mid feb or so).
This unblocks Dependabot from moving forward 👍
Most helpful comment
Is this still an issue? I'd love to be able to use Dependabot with CocoaPods!