Skip to content

Commit 4b0c737

Browse files
authored
Document user facing api changes introduced in 3280 and 3641 (#3674)
1 parent c3bd142 commit 4b0c737

File tree

1 file changed

+12
-4
lines changed

1 file changed

+12
-4
lines changed

CHANGELOG.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,15 @@
11
Note: This is in reverse chronological order, so newer entries are added to the top.
22

3-
Swift v.Next
3+
Swift 5.6
44
-----------
55
* [#3649]
66
Semantic version dependencies can now be resolved against Git tag names that contain only major and minor version identifiers. A tag with the form `X.Y` will be treated as `X.Y.0`. This improves compatibility with existing repositories.
77

8+
* [#3641]
9+
Soft deprecate `.pacakge(name:, url:)` dependency syntax in favour of `.pacakge(url:)`, given that an explciit `name` attribute is no longer needed for target depedendencies lookup.
810

11+
* [#3641]
12+
Adding a dependency requirement can now be done with the convenience initializer `.package(url: String, exact: Version)`.
913

1014
Swift 5.5
1115
-----------
@@ -17,11 +21,12 @@ Swift 5.5
1721

1822
* [#3292]
1923
Adding a dependency requirement can now be done with the convenience initializer `.package(url: String, branch: String)`.
20-
21-
* [#3316]
22-
Test targets can now link against executable targets as if they were libraries, so that they can test any data strutures or algorithms in them. All the code in the executable except for the main entry point itself is available to the unit test. Separate executables are still linked, and can be tested as a subprocess in the same way as before. This feature is available to tests defined in packages that have a tools version of `5.5` or newer.
2324

25+
* [#3280]
26+
A more intuitive `.product(name:, package:)` target depedendency syntax is now accepted, where `package` is the package identifier as defined by the package URL.
2427

28+
* [#3316]
29+
Test targets can now link against executable targets as if they were libraries, so that they can test any data strutures or algorithms in them. All the code in the executable except for the main entry point itself is available to the unit test. Separate executables are still linked, and can be tested as a subprocess in the same way as before. This feature is available to tests defined in packages that have a tools version of `5.5` or newer.
2530

2631
Swift 5.4
2732
-----------
@@ -146,7 +151,10 @@ Swift 3.0
146151
[#1489]: https://github.com/apple/swift-package-manager/pull/1489
147152
[#1604]: https://github.com/apple/swift-package-manager/pull/1604
148153
[#2937]: https://github.com/apple/swift-package-manager/pull/2937
154+
[#3280]: https://github.com/apple/swift-package-manager/pull/3280
149155
[#3292]: https://github.com/apple/swift-package-manager/pull/3292
150156
[#3310]: https://github.com/apple/swift-package-manager/pull/3310
151157
[#3316]: https://github.com/apple/swift-package-manager/pull/3316
152158
[#3410]: https://github.com/apple/swift-package-manager/pull/3410
159+
[#3641]: https://github.com/apple/swift-package-manager/pull/3641
160+
[#3649]: https://github.com/apple/swift-package-manager/pull/3649

0 commit comments

Comments
 (0)