Release 0.26.1 · CocoaPods/CocoaPods

CocoaPods now creates and hides the schemes of its targets after every
installation. The schemes are not shared because the flag which keeps track
whether they should be visible is a user only flag. The schemes are still
present and to debug a single Pod it is possible to make its scheme visible
in the Schemes manager of Xcode. This is rarely needed though because the
user targets trigger the compilation of the Pod targets.
Fabio Pelosin
#1185
Installations which don't integrate a user target (lint subcommands and
--no-integrate option) now set the architecture of OS X Pod targets to
$(ARCHS_STANDARD_64_BIT) (Xcode 4 default value for new targets). This
fixes lint issues with Xcode 4.
Fabio Pelosin
#1185
Further improvements to the organization of the Pods project
- The project is now is sorted by name with groups at the bottom.
- Source files are now stored in the root group of the spec, subspecs are not
  stored in a Subspec group anymore and the products of the Pods all are
  stored in the products group of the project.
- The frameworks are referenced relative to the Developer directory and
  namespaced per platform.
Fabio Pelosin
#1389
#1420
Added the documentation_url DSL attribute to the specifications.
Fabio Pelosin
#1273

The search paths of vendored frameworks and libraries now are always
specified relatively.
Fabio Pelosin
#1405
Fix an issue where CocoaPods would fail to work when used with an older
version of the Active Support gem. This fix raises the dependency version to
the earliest compatible version of Active Support.
Kyle Fuller
#1407
CocoaPods will not attempt to load anymore all the version of a specification
preventing crashes if those are incompatible.
Fabio Pelosin
#1272

Provide feedback