Prepare next release - #46
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 4, 2026 08:10
672e128 to
9b8bac7
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
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.0
Minor Changes
#47
95c4250Thanks @germ-mark! -ValidatedForAnchorgains an.agentUpdateV2case (CommProposal's tag 6 waspreviously unhandled on the anchor path —
default: throw .unsupported), mirroringthe existing card-side validation.
mailboxGrantVersionmoves2.4.0→3.1.0:the original threshold assumed nothing had ever stamped a version at or above it
(the property that made
pqCapableVersion= 2.3.0 sound), butpqDomainSeparationVersion= 3.0.0 is already stamped by every PQ connection, so a2.4.0 gate would have let an old PQ build believe it could parse tag 6 and then drop
the message. 3.1.0 clears every currently-stamped tier.
AgentUpdateV2.formatForSigningnow leads with a case discriminator(
"CommProposal.agentUpdateV2"): a proposal's tag byte is not covered by itspayload's signature, and while tags 1–5 shipped with frozen preimages (kept apart
by structural parse incompatibility alone), tag 6 has never shipped — so it gets
cryptographic case binding from birth, free. Wire bytes are unchanged; only the
signed preimage moves.
#45
9d58f1cThanks @germ-mark! - Add mailbox-v2 wire types (GER-1965/1966/1967):swift-cborpinned at the samerevision as CoreAppLogic, a
DeterministicCborseam, andMailboxGrant(
{authKey, serviceHost, expiration}) withaddress/putTagHMAC-SHA256derivation, cross-validated against germ-service's test vectors. A
ProtocolAddress <-> MailboxGrantbridge lets a grant ride the existingidentifierfield on the wire-frozen PQ establishment surfaces (an authKey's32 decoded bytes never collide with a legacy
crypto.randomUUID()address's 27) with zero arity change.AgentUpdateV2(grants only) rides a newCommProposaltag, emitted only to peers observed >=mailboxGrantVersion(2.4.0) — existing proposal tags and the classical
AgentUpdate/ProtocolAddresswire format are unchanged (fixture-pinned).