Repository navigation
chore(deps): propagate Samva SDK 0.35 and CLI 0.30 - #107
Merged
Merged
Conversation
[Medium impact] The PR appears safe to merge; no actionable issues remain. SummaryUpdates maintained integrations to Samva SDK 0.35 and CLI 0.30.
Reviews (2) · Last reviewed commit: "docs(plugin): describe non-email channel..." · Reviewed by Greptile |
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.
Propagate
samva0.35.0 and@samva/cli0.30.0 into the maintained integrations. Both published adapters require only the current SDK minor and receive minor Tegami notes for the peer-range change.Source release: https://github.com/AryaLabsHQ/samva/pull/2679, merge commit
d85da153c6. Reviewed SDK, CLI, and webhooks changelogs from the producer'sorigin/main, plus contracts and SDK declarations (also checked at the merge commit). Producer checkout was read only.messages/group.tsdeclares send fields anddeveloper/group.tsdeclareseventTypes;http-api.tsand SDK Effect internal client reject excess properties. Better Auth renderer returns only subject/html/text; Email SDK maps supported fields explicitly (attachment size is declared). Other sends construct explicit bodies, not response spreads. Webhook calls already use eventTypes. Extension manifesteventsis a separate SDK mailbox contract. CLI mailbox JSON declares name/metadata. No undeclared caller fields found.Validation (Bun 1.4.4, Node 24.22.1, Deno 2.9.8; CI pins Deno 2.9.5):
bun install,bun install --frozen-lockfile: passed.bun run build --continue(12/12 tasks),bun run typecheck --continue(18/18 tasks),bun run test(7 files, 139 tests),bun run lint, andbun run format:check: all passed. --continue preserves failure status while allowing independent workspaces to finish.bun run validate:agent-plugin,bun --filter tsx-template-samva check,git diff --check: passed.Validation after updating from main: head
6093a077284a228809d683784f1a450e65cc8564merges8e3d4bband preserves main's README positioning and plugin description. Freshbun run format:check,bun run validate:agent-plugin, andgit diff --checkpassed. Build, typecheck, and 139-test results above ran on083baed5338cd486bf5fc26f99c5f0e7c1583804and remain applicable: the only changes since that head are README copy and a plugin display description; source, manifests, lockfile, and tested contracts are identical.