Prepare next release - #60
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/autonomous-comm-protocol@1.13.0
Minor Changes
#59
d647004Thanks @germ-mark! - Widen theswift-cryptodependency tofrom: "5.0.0"as part of the org-wideswift-crypto 5 migration.
GermConveniencemoves to its released 0.10.0 (the swift-crypto-5 release).AtprotoTypesis revision-pinned to its swift-crypto-5 commit(Widen swift-crypto dependency to from: 5.0.0 AtprotoTypes#69) until it cuts a release, because its released
line still caps swift-crypto at
..<5.0.0.No source changes were required.
Secret-bytes audit (no adoption). The package holds key material — the
identity signing key (
IdentityPrivateKey, aCryptoKit/swift-crypto privatekey type) and
TypedKeyMaterial.keyData, which is either a symmetric key or anHPKE-encapsulated (non-secret) byte string disambiguated by
algorithm. MovingkeyDataintoSecretByteswould change a wire/format-level type shared acrossthe codec, and the private keys already live in swift-crypto's own key types
rather than a plaintext field, so swift-secret-bytes is deliberately not
adopted here.