Prepare next release - #54
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
August 18, 2026 23:30
b8f2554 to
e5c856f
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 18, 2026 23:31
e5c856f to
3ed449a
Compare
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.12.3
Patch Changes
#56
c72d48cThanks @germ-mark! - Depend on swift-crypto and import Crypto instead of CryptoKit, so the packagebuilds on Linux and Android. On Apple platforms swift-crypto delegates to
CryptoKit, so behavior is unchanged. Raises the AtprotoTypes floor to 0.5.0,
the first release that builds on those platforms.
#55
06c3fa9Thanks @germ-mark! - Require swift-bases 0.3.0 in the manifest.MailboxGrantis written against 0.3.0's throwingData(base64URLEncoded:), butPackage.swiftstill permitted 0.2.x — and consumers resolve from the manifest, not this package'sPackage.resolved, so the previous change expressed the adoption only locally.#53
e5de983Thanks @germ-mark! - Adopt swift-bases 0.3.0's throwingData(base64URLEncoded:)inMailboxGrant.mailboxGrant. No behavior change — a decode failure still yieldsnilfrom that computed property — but this was a source break for anyone whose resolved dependency graph floats past swift-bases 0.2.1.