Add complete memory module#43
Merged
Merged
Conversation
Change-Id: Iea5dbdcf29c9ac1dd1b8d55f824f9e96e82cfb8d
Change-Id: I5e3e201d94cdbe7a239f23a7dbd4d8fd89726b80
heimanba
marked this pull request as ready for review
July 20, 2026 16:33
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.
Summary
betadist-tag instead ofbeta-<sha>-<date>Why
Memory stores were previously only partially represented as declarative resources. Users could attach stores to agents and deployments, but could not manage the complete Memory lifecycle consistently through the SDK and CLI.
Provider APIs also differ in path formats, version routes, pagination, metadata update semantics, and concurrency controls. Centralizing those differences behind a portable contract prevents provider-specific behavior from leaking into callers.
The beta release workflow computed the correct
betachannel but did not pass it to the publish script. The script then inferred the npm dist-tag from the full snapshot suffix and produced tags such asbeta-ddef91c-20260720.Impact
Users can now create, inspect, update, archive, and delete Memory stores and entries through the SDK and CLI. Declarative updates reconcile configured seed entries in place while preserving runtime-learned memories.
Beta packages keep unique immutable versions such as
1.2.3-beta-ddef91c-20260720, while npm consistently publishes them under thebetadist-tag.Validation
bun test packages/sdk/tests— 594 tests passedbun run verify:scopedbun scripts/verify.ts push— full workspace typecheck, architecture checks, tests, and changed-file lint passed