Update dependency apple/swift-crypto to v5 - #12
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
from: "4.5.0"→from: "5.0.0"Release Notes
apple/swift-crypto (apple/swift-crypto)
v5.0.0Compare Source
Swift Crypto 5.0 Release Notes
Swift Crypto 5.0 aligns the cross-platform API surface with CryptoKit as shipped in Xcode 27 (CryptoKit-383.2.1), and takes the opportunity to streamline the package for both adopters and maintainers.
Most users will be able to depend on the 1.0.0, 2.0.0, 3.0.0, 4.0.0, or 5.0.0 series of releases.
To do so, please use the following dependency in your
Package.swift:Requires Swift 6.2
The package now declares 6.2 as the minimum Swift version in its package manifest.
New span-based API
CryptoKit's new non-allocating, span-based entry points are now available cross-platform:
SymmetricKeygainsbytes: RawSpan,init(copying: RawSpan),init(copyingWithZeroing: inout MutableRawSpan), andinit(size:initializingWith:)which initializes the key through aninout OutputRawSpan.HashFunctiongainsupdate(bytes: RawSpan)andhash(bytes: RawSpan), andDigestgainsinit?(copying: RawSpan).HMACgainsauthenticationCode(for: RawSpan, using:).HKDFgainsderiveKey(inputKeyMaterial:salt:info:output:)writing into aninout OutputRawSpan, along with span-basedextractandexpand. The existingDataProtocoloverload now has a fast path for contiguous salt and info.AES.GCMandChaChaPolygain in-placeseal(inPlace:using:nonce:authenticating:tag:)andopen(inPlace:using:nonce:authenticating:tag:)overMutableRawSpan, and theirNoncetypes gainbytes: RawSpanandinit(copying: RawSpan).Single-use KEM keys
A new
KEMOneTimePrivateKeyprotocol, refining~CopyableandSendable, provides aconsuming func decapsulate(_:)so a decapsulation key cannot be reused. Conforming types areMLKEM768.OneTimePrivateKey,MLKEM1024.OneTimePrivateKey, andXWingMLKEM768X25519.OneTimePrivateKey.Extensible enums
Historically Swift Crypto needed a new major version each time CryptoKit added a case to a non-frozen enum, because Swift Crypto is not built with library evolution. All public non-frozen enums are now marked
@nonexhaustive(SE-0487), which should remove that reason for future major bumps. Adopters who do not switch over these enums should not need to widen their version constraints again.Other changes
@_spi(...) publichave been made internal; they were never intended to be available.@availableannotations have been removed fromCrypto; they are unused in all supported compilation modes.finalECDSASignature.derBytes, is removed.Build and packaging
CCryptoBoringSSLShimstarget is removed, along with allbindMemory(to:)calls..gybtemplates for nonces, digests, ECDH, ECDSA, MLDSA, and MLKEM are removed and the generated Swift is checked in. The BoringSSL backend templates for MLDSA and MLKEM remain.#if canImport(CryptoKit); branches that could never be taken are gone.-Wshorten-64-to-32for BoringSSL andmacro-redefinedfor XKCP. CI builds with-warnings-as-errors.Commits
The changes in this release were reviewed and merged to the 5.x branch during the beta period:
0a26a9e[5.x] Align with CryptoKit APIs from Xcode 27 beta 1 (#442)8ee9962[5.x] Align with CryptoKit APIs from Xcode 27 beta 2 (#444)ce8db47[5.x] Align with CryptoKit APIs from Xcode 27 beta 4 (#453)15b0fb5[5.x] Adopt CheckImplementationOnly and CI with -warnings-as-errors (#454)b3746b1[5.x] Remove bindMemory(to:) calls and the CCryptoBoringSSLShims target (#455)57782dc[5.x] Remove duplicate imports from gyb-generated MLDSA backend code (#458)2c45ca2[5.x] Remove unused internal code path: ECDSASignature.derBytes (#457)33785f6[5.x] Mark some class types as final (#456)2e074ef[5.x] Remove native SwiftPM build-system workaround in CI (#461)20f9049[5.x] Align with CryptoKit from Xcode 27 beta 6 (#462)Full Changelog: apple/swift-crypto@4.5.2...5.0.0
v4.5.2Compare Source
What's Changed
SemVer Patch
Other Changes
New Contributors
Full Changelog: apple/swift-crypto@4.5.1...4.5.2
v4.5.1Compare Source
What's Changed
SemVer Patch
47d3869Other Changes
Full Changelog: apple/swift-crypto@4.5.0...4.5.1
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.