Move engine dependencies onto swift-crypto 5 - #140
Merged
Merged
Conversation
Org-wide swift-crypto 5 move, carried by revision-pinning twomlspq-swift, swift-mls, and autonomous-comm-protocol to their swift-crypto-5 branches and moving swift-secret-bytes to 0.5.0. No source changes. Co-Authored-By: Claude Code <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 10d0d81 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Following the GermConvenience 0.10.0 release, the remaining revision pins move to the current tips of their swift-crypto-5 branches so every requester agrees on one revision. Replace with released versions as each cuts. Co-Authored-By: Claude Code <noreply@anthropic.com>
swift-mls 0.1.3 is cut and carries the swift-crypto 5 move; twomlspq-swift's branch tip now consumes it, so this pin moves to match. Co-Authored-By: Claude Code <noreply@anthropic.com>
Per-dependency repin: twomlspq-swift 0.2.0 is released and carries the swift-crypto 5 move, so the revision pin drops. The ACP pin stays until it releases. Co-Authored-By: Claude Code <noreply@anthropic.com>
.upToNextMinor(from: "0.5.0") fences out 0.6.0; from: keeps the 0.5.x floor while admitting it once it cuts. Co-Authored-By: Claude Code <noreply@anthropic.com>
Both releases carry the widened swift-secret-bytes pin (from: 0.5.0), which is what makes 0.6.0 reachable through this package. Co-Authored-By: Claude Code <noreply@anthropic.com>
Per-dependency repin: the dependency is released and carries the swift-crypto 5 move, so the revision pin drops. No revision pins remain here. Co-Authored-By: Claude Code <noreply@anthropic.com>
Merged
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
1 participant
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.
What
Part of the org-wide swift-crypto 5 migration. This package has no direct
swift-cryptorequirement — itsswift-cryptoarrives through swift-mls / swift-secret-bytes — so the move is carried by revision pins:twomlspq-swift→ its swift-crypto-5 branch (Move to swift-crypto 5 and swift-secret-bytes 0.5.0 twomlspq-swift#60)swift-mls→ its swift-crypto-5 branch (Move to swift-crypto 5 and swift-secret-bytes 0.5.0 swift-mls#103)autonomous-comm-protocol→ its swift-crypto-5 branch (Widen swift-crypto dependency to from: 5.0.0 autonomous-comm-protocol#59)swift-secret-bytes→.upToNextMinor(from: "0.5.0")(its swift-crypto-5 release)All temporary; replace with released versions once each cuts.
No source changes were required.
Note
swift buildon a macOS host fails inSources/TwoMLSPQBindingon a UniFFI-bindings/xcframework mismatch — a freshly-clonedmainfails identically, and the repo's CI builds the xcframework locally (TWOMLSPQ_LOCAL_XCFRAMEWORK), so this is expected without a local Rust build, not a regression from this change.This unblocks germDM's CoreAppLogic, whose graph could not resolve against
swift-secret-bytes0.5.0 while TwoMLSPQ pinned..<0.5.0.automatically drafted by a Claude llm
🤖 Generated with Claude Code