Carthage v0.34.0 Release Notes
Release Date: 2019-10-21 // over 4 years ago-
π β οΈ Carthage source only builds on Xcode 10.0+, thus requiring macOS High Sierra 10.13.6. β οΈ
β Additional workarounds to enable Xcode 11.0, 11.1, and 11.2 betas have been added; see below.
π Fixed
- π ASCII alphabet for Semantic Version pre-release and build metadata components now includes uppercase and lowercase W, fixing an omission and completing the alphabet (#2805 #2806). Thanks @drakerr!
- βͺ Workaround Swift 5.1 compiler crash bug to allow the compilation of Carthage itself on Xcode 11, Xcode 11.1, and Xcode 11.2 betas (#2859). Thanks @michaelmcguire!
π₯ Breaking β For Apps Importing Carthage Kit
β Removed β as a library dependency β
SwiftPM
andllbuild
and reinstatedstruct CarthageKit.SemanticVersion
.π¦ A bug in the-tool-SwiftPM's package resolution resulted in disregard for the (crucial) βresolved fileβ when resolving branch-based dependencies.
π Which would put us in the position of needing any commit of
apple/swift-package-manager
that didnβt specify its dependency onapple/swift-llbuild
in the branch-based style.Also criteria for the above, working Swift 4.2.X manifests and compilation and working Swift 5.X manifests and compilation.
π¦ No such commit of
apple/swift-package-manager
could be found.In addition, some confusion around
llbuild
'ssqlite3
linkage made criteria even more confusing.- Some initializers and methods on
struct Carthage.SemanticVersion
have differences from the previous incarnation found in v0.33.0. - β
Reinstate
struct CarthageKit.SemanticVersion
in all callsites in codebase and tests, removingSPMUtility.Version
. - π No longer necessary to
import struct Foundation.URL
with the removed import of SPMUtility. - π Makefile removes complications which previously supported
llbuild
'ssqlite3
linkage. - Working Swift 4.2.X compilation is necessary to support building for macOS High Sierra on Homebrew bottling infrastructure.
Important
β‘οΈ Future updates will address Catalyst and building of XCFrameworks. Thank you for your patience.
Thank you to @jdhealy, @sstadelman, @tmspzz, @giginet, @olejnjak, and @ikesyo for improvements to the codebase and the infrastructure.
Thank you to @mdiep, @tmspzz, @giginet, and @ikesyo for reviewing pull requests!