With Cocoapods 1.0.0 being close to its release date, we want to remind you that there are breaking changes being introduced in this major new version. You can read about this in more detail in this blog post.
By default, we will run the
pod install command to install all the pods specified in your project’s
Podfile. This command will use the version of Cocoapods that is pre-installed in the OS X build image, right now it is
0.39.0. If you generate your
Podfile with Cocoapods
1.0.0, this might result in a build failure.
To ensure that the version of Cocoapods used in your OS X project is correct at all times, independently of the version pre-installed in our build image, we suggest that you commit a
Gemfile to your repo.
Gemfile you will be able to specify the version of Cocoapods that you would like to use. Here is an example
# Gemfile source 'https://rubygems.org' gem 'cocoapods', '= 0.39.0'
If we detect a
Podfile and a
Gemfile at the same time, we will run the following commands:
bundle exec pod install
pod install with the version of Cocoapods specified in your
By adding a
Gemfile you will be able to choose your own timing around upgrading to Cocoapods 1.0.0—and will make sure that you control the version of Cocoapods being used in your build at every point.
You can find more information about the software pre-installed in our OS X build image in this doc.