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
and to your target, add `Crypto` to your dependencies. You can then `import Crypto` to get access to Swift Crypto's functionality.
@@ -108,7 +108,7 @@ If you believe you have identified a vulnerability in Swift Crypto, please [repo
108
108
109
109
### Swift versions
110
110
111
-
The most recent versions of Swift Crypto support Swift 5.7 and newer. The minimum Swift version supported by Swift Crypto releases are detailed below:
111
+
The most recent versions of Swift Crypto support Swift 6 and newer. The minimum Swift version supported by Swift Crypto releases are detailed below:
112
112
113
113
Swift Crypto | Minimum Swift Version
114
114
--------------------|----------------------
@@ -119,7 +119,8 @@ Swift Crypto | Minimum Swift Version
119
119
`3.1.0 ..< 3.3.0` | 5.7
120
120
`3.3.0 ..< 3.8.0` | 5.8
121
121
`3.9.0 ..< 3.13.0` | 5.9
122
-
`3.13.0 ...` | 5.10
122
+
`3.13.0 ..< 4.0.0` | 5.10
123
+
`4.0.0 ...` | 6.0
123
124
124
125
### Compatibility
125
126
@@ -131,10 +132,14 @@ SemVer and Swift Crypto's Public API guarantees should result in a working progr
131
132
132
133
Swift Crypto 2.0.0 was released in September 2021. The only breaking change between Swift Crypto 2.0.0 and 1.0.0 was the addition of new cases in the `CryptoError` enumeration. For most users, then, it's safe to depend on either the 1.0.0 _or_ 2.0.0 series of releases.
133
134
135
+
Swift Crypto 3.0.0 was released in September 2023. Again the only breaking change was the addition of new cases in the `CryptoError` enumeration, so most users can safely depend on the 1.0.0, 2.0.0, or 3.0.0 series of releases.
136
+
137
+
Swift Crypto 4.0.0 was released in September 2025. Again the only breaking change was the addition of new cases in the `CryptoError` enumeration, so most users can safely depend on the 1.0.0, 2.0.0, 3.0.0, or 4.0.0 series of releases. Note that in this release `_CryptoExtras` was renamed to `CryptoExtras`. The old products and targets have been kept around for compatibility reasons, but users depending only on new code should use `CryptoExtras` not `_CryptoExtras`.
138
+
134
139
To do so, please use the following dependency in your `Package.swift`:
0 commit comments