Prepare next release - #141
Merged
Merged
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@germ-network/two-mls-pq@0.20.0
Minor Changes
#140
e7132a8Thanks @germ-mark! - Move the MLS engine dependencies onto swift-crypto 5, as part of the org-wideswift-crypto 5 migration. This package has no direct
swift-cryptorequirement (its
swift-cryptoarrives through swift-mls / swift-secret-bytes);the move is carried by revision-pinning those:
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-5release)
All revision pins are 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; thatfailure is identical on
mainand predates this change.)