Repository navigation
Release 0.23.2 - #637
Merged
nissa-seru merged 4 commits intoOct 20, 2026
Merged
Release 0.23.2#637
Conversation
…rites The 0.23 line's pick of anima-research#622. A channel server's metadata, a channels/incoming message's `metadata` or a push event's `origin`, was spread into the metadata its message is stored with, and the host wrote its own fields over it. Where the host wrote nothing, a server's copy of a key the host trusts on its own was stored, so a server's message could pass for one the host wrote: with `kind: "discord-send-failed"`, a message left unread in a conversation fork's window made the host tell the primary, when the fork was released, that the fork's reply had failed (anima-research#611). - HOST_METADATA_KEYS lists the keys only the host writes that some reader in this line takes alone: system (isConversationalInjection, shedNewestTurn), kind (the failed-reply readers), draftOwner and draftIds (the drafts' catch-up readers), tuneOut (the residents' viewFilter and the held-row readers), coalescingSubject (the restore's published check, beside eventId), deferredWriteId (boot's dedup; a fork's channel write goes straight to the fork's store), external (the held-write match, the module registry's and the Discord module's lookups of their own rows) and openaiResponsesItems (membrane's mark of an imported Responses history). It's anima-research#622's set without `firstView`, which this line doesn't have. - withoutHostKeys drops them from both ingresses, and logs the first drop of each key from each server, naming both and never the value. - The tool boundary hands membrane each injected message as its participant and content alone: a stored row's metadata is the host's record, not input for membrane. Tests: ingress-host-keys (both lanes over the fixture MCPL child, and the log line for two servers in both lanes); route-failure-targeting (a DM whose metadata carries every key and claims to be a failed-reply notice reaches the fork's window without them, and tells the primary nothing when the fork is released); present-while-acting (an injected message reaches membrane as participant and content only). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings 0.23.2's release commit back to main: the ## 0.23.2 section of CHANGELOG.md and package.json's version. Source and tests merge to main's own text, since the release's change is a port of anima-research#622, which main already holds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0.23.2's section carries it. The merge leaves main's copy in place, since v0.23.1 never had it, and without this main's next release would list the fix a second time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 brings agent-framework 0.23.2's release commit back to
main. 0.23.2 was cut fromv0.23.1(f91ca75a) with one change ported onto it, #622's fix (83152470), and thennpm version patch(7122cb73), which folded the fix's fragment into## 0.23.2 — 2026-10-20.v0.23.2is tagged at7122cb73, and npm's 0.23.2 was published from it.What this branch is
758bb9f2mergesrelease/0.23.xat7122cb73intomainatc602d868. Its source and tests merge tomain's own text, since the release's change is a port of fix(mcpl): store a server's metadata without the keys only the host writes #622, whichmainalready holds.a8a68d7cdeleteschangelog.d/ingress-host-keys.fixed.md. The release folded that fragment on its own line, butmainkept the copy fix(mcpl): store a server's metadata without the keys only the host writes #622 merged, and a merge leaves it in place becausev0.23.1never had it. Without the deletion,main's next release would list the fix a second time.Against
main, the branch adds the## 0.23.2section toCHANGELOG.md, deletes that one fragment, and changespackage.json's version from 0.23.1 to 0.23.2. Nothing else differs. It merges withmainatc602d868without a conflict.0.22.5, published from
release/0.22.xthe same day, doesn't merge back, as 0.22.4 didn't.Release cut and description written by Ada-1017 (Claude Opus 5.5).
Description checked and posted by Daniel-2612 (Claude Opus 5.5).
🤖 Written using Anthropic's Claude Opus 5.5 through the Rookery's tooling, and posted from the shared
nissa-seruaccount.