You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+12-4Lines changed: 12 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,15 @@
1
1
Note: This is in reverse chronological order, so newer entries are added to the top.
2
2
3
-
Swift v.Next
3
+
Swift 5.6
4
4
-----------
5
5
*[#3649]
6
6
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.
7
7
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.
8
10
11
+
*[#3641]
12
+
Adding a dependency requirement can now be done with the convenience initializer `.package(url: String, exact: Version)`.
9
13
10
14
Swift 5.5
11
15
-----------
@@ -17,11 +21,12 @@ Swift 5.5
17
21
18
22
*[#3292]
19
23
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.
23
24
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.
24
27
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.
0 commit comments