Skip to content

Releases: Carthage/Carthage

0.5: Pit of Loneliness

25 Dec 19:11
Compare
Choose a tag to compare

Framework authors can now create a Cartfile.private, to describe private dependencies that should not be exported to parent projects.

For an example of this in action, see the changes made to the dependencies of Carthage itself.

For a full list of changes, see the 0.5 milestone.

0.4: Carthage Unpinned

22 Dec 21:13
Compare
Choose a tag to compare

This release adds the ability to pin to arbitrary branches or tags in your Cartfile! 🎉

This release also includes a workaround for errors when submitting to the iOS App Store. See the updated README for instructions on setting up your iOS app project appropriately.

Finally, there have been some breaking changes to the Carthage directory structure, so we can lock it down before 1.0. The new artifact layout looks like this:

Cartfile
Cartfile.resolved
Carthage/
    Build/
    Checkouts/

When you run carthage build, carthage checkout, or carthage update in a project with the old layout, it will be automatically migrated to the new structure. However, you will have to manually update your project to find its dependencies in the new location.

For a full list of changes, see the 0.4 milestone.

0.3.1: The Git That Keeps On Gitting

19 Dec 19:48
Compare
Choose a tag to compare

This release is meant to address the recently announced Git vulnerability.

Instead of always using /usr/bin/git, Carthage will now use whichever version of git is in your $PATH. This means that /usr/local/bin/git can be prioritized over Apple's vulnerable build of Git now.

You still must install a patched version of Git yourself, and ensure it lies first in your $PATH.

Other minor fixes include:

This version is available via Homebrew. Simply run brew update && brew install carthage.

0.3: Submodule Inception

04 Dec 04:56
Compare
Choose a tag to compare

Carthage 0.3 adds a new --use-submodules flag to the bootstrap, update, and checkout commands, allowing you to add dependencies as Git submodules, instead of simply checking out their source code into your project's directory.

This is intended to make framework development easier, as well as provide a way to preserve dependencies' version history without polluting your project's history.

For more information, please see the section in the README or consult carthage help.

This release also includes a major fix for a Cartfile.lock ordering bug that can result in failed builds.

0.2.2

01 Dec 20:15
Compare
Choose a tag to compare

Fixed:

0.2.1

01 Dec 19:04
Compare
Choose a tag to compare

Major fixes and improvements:

Known issues include:

We hope to fix both of these issues in the very next release.

0.2

19 Nov 18:42
Compare
Choose a tag to compare
0.2

This release improves documentation, polishes up the published CarthageKit API, and fixes stdout being hardcoded in CarthageKit.

Known issues include:

0.1 (initial release)

18 Nov 06:41
Compare
Choose a tag to compare