Note: This is in reverse chronological order, so newer entries are added to the top.
-
-
Improvements
Package
manifests can now have any combination of leading whitespace characters. This allows more flexibility in formatting the manifests.SR-13566 The Swift tools version specification in each manifest file now accepts any combination of horizontal whitespace characters surrounding
swift-tools-version
, if and only if the specified version ≥5.4
. For example,//swift-tools-version: 5.4
and// swift-tools-version: 5.4
are valid.All Unicode line terminators are now recognised in
Package
manifests. This ensures correctness in parsing manifests that are edited and/or built on many non-Unix-like platforms that use ASCII or Unicode encodings. -
API Removal
ToolsVersionLoader.Error.malformedToolsVersion(specifier: String, currentToolsVersion: ToolsVersion)
is replaced byToolsVersionLoader.Error.malformedToolsVersionSpecification(_ malformation: ToolsVersionSpecificationMalformation)
.ToolsVersionLoader.split(_ bytes: ByteString) -> (versionSpecifier: String?, rest: [UInt8])
andToolsVersionLoader.regex
are together replaced byToolsVersionLoader.split(_ manifest: String) -> ManifestComponents
. -
Source Breakages for Swift Packages
The package manager now throws an error if a manifest file contains invalid UTF-8 byte sequences.
-
-
The
swiftLanguageVersions
property no longer takes its Swift language versions via a freeform Integer array; instead it should be passed as a newSwiftVersion
enum array. -
The
Package
manifest now accepts a new type of target,systemLibrary
. This deprecates "system-module packages" which are now to be included in the packages that require system-installed dependencies. -
Packages can now specify a dependency as
package(path: String)
to point to a path on the local filesystem which hosts a package. This will enable interconnected projects to be edited in parallel. -
The
generate-xcodeproj
has a new--watch
option to automatically regenerate the Xcode project if changes are detected. This uses thewatchman
tool to detect filesystem changes. -
Scheme generation has been improved:
- One scheme containing all regular and test targets of the root package.
- One scheme per executable target containing the test targets whose dependencies intersect with the dependencies of the exectuable target.
-
SR-6978 Packages which mix versions of the form
vX.X.X
withY.Y.Y
will now be parsed and ordered numerically. -
#1489 A simpler progress bar is now generated for "dumb" terminals.
-
#1485 Support has been added to automatically generate the
LinuxMain
files for testing on Linux systems. On a macOS system, runswift test --generate-linuxmain
. -
SR-5918
Package
manifests that include multiple products with the same name will now throw an error.
-
The generated Xcode project creates a dummy target which provides autocompletion for the manifest files. The name of the dummy target is in format:
<PackageName>PackageDescription
. -
--specifier
option forswift test
is now deprecated. Use--filter
instead which supports regex.
-
The package manager now supports writing Swift 3.0 specific tags and manifests, in order to support future evolution of the formats used in both cases while still allowing the Swift 3.0 package manager to continue to function.
-
Test modules now must be named with a
Tests
suffix (e.g.,Foo/Tests/BarTests/BarTests.swift
). This name also defines the name of the Swift module, replacing the oldBarTestSuite
module name. -
It is no longer necessary to run
swift build
before runningswift test
(it will always regenerates the build manifest when necessary). In addition, it now accepts (and requires) the same-Xcc
, etc. options as are used withswift build
. -
The
Package
initializer now requires thename:
parameter.