Thanks to visit codestin.com
Credit goes to github.com

Skip to content

chore(agent-cache): release v0.11.0 (streaming cache) + fix TS build#306

Merged
KIvanow merged 1 commit into
masterfrom
chore/agent-cache-0.11.0
Jul 7, 2026
Merged

chore(agent-cache): release v0.11.0 (streaming cache) + fix TS build#306
KIvanow merged 1 commit into
masterfrom
chore/agent-cache-0.11.0

Conversation

@KIvanow

@KIvanow KIvanow commented Jul 7, 2026

Copy link
Copy Markdown
Member

Summary

#262 shipped wrapStream (streaming response caching for the Vercel AI SDK adapter) but left three loose ends. This releases the feature and fixes the build.

Changes

  • Version: bump @betterdb/agent-cache 0.10.0 → 0.11.0 (new backward-compatible feature).
  • Changelog: feat(agent-cache/ai): cache streaming LLM responses via wrapStream #262 filed the entry under a stale, already-released [0.8.0] - Unreleased heading; retitled to [0.11.0] - 2026-07-07.
  • TS build (package tsc was failing):
    • Add @ai-sdk/provider as a direct devDependency — ai.ts imports its LanguageModelV3* types, which pnpm's strict layout hid as a transitive dep of ai.
    • ai.test.ts: type the mock params as LanguageModelV3CallOptions and add a streamCall() helper supplying the doGenerate/model fields the middleware call signature now requires (tests exercise only the streaming path).
  • Docs: the Vercel AI SDK adapter now caches doStream as well as doGenerate; moved streaming out of "Known limitations" (only tool-call streams remain uncached; cached streams replay as a single chunk).

Verification

  • tsc --noEmit clean on packages/agent-cache.
  • vitest run ai.test.ts — 5/5 pass.
  • Lockfile change scoped to the single @ai-sdk/provider entry.

Companion website update removes the matching "streaming not cached" copy (separate repo).


Note

Low Risk
No adapter runtime changes in this diff—version bump, dev dependency, test helpers, and documentation only.

Overview
Releases @betterdb/agent-cache v0.11.0 and aligns packaging/docs with streaming cache support for the Vercel AI SDK adapter (wrapStream), which was added in a prior change.

Release: version 0.10.0 → 0.11.0; changelog retitled from a stale [0.8.0] - Unreleased block to [0.11.0] - 2026-07-07 documenting streaming caching behavior.

Build/tests: adds @ai-sdk/provider as a direct devDependency so LanguageModelV3* types resolve under pnpm; ai.test.ts types mocks as LanguageModelV3CallOptions and uses a streamCall() helper so wrapStream tests satisfy the full middleware signature (doGenerate, model, etc.).

Docs: Vercel AI SDK section and “Known limitations” now state that doStream is cached (replay as one text-delta + finish; tool-call streams still uncached); LangChain/LlamaIndex remain non-streaming only.

Reviewed by Cursor Bugbot for commit d946699. Bugbot is set up for automated code reviews on this repo. Configure here.

#262 shipped wrapStream (streaming response caching for the Vercel AI SDK
adapter) but left the package version at 0.10.0, filed the changelog entry
under a stale "[0.8.0] - Unreleased" heading, and didn't typecheck cleanly.

Release:
- Bump packages/agent-cache to 0.11.0 (new backward-compatible feature).
- Retitle the changelog entry to [0.11.0] - 2026-07-07.

TS build fixes (package tsc was failing):
- Add @ai-sdk/provider as a direct devDependency — ai.ts imports its
  LanguageModelV3* types, which pnpm's strict layout hid as a transitive dep.
- ai.test.ts: type the mock params as LanguageModelV3CallOptions and add a
  streamCall() helper that supplies the doGenerate/model fields the middleware
  call signature requires (tests exercise only the streaming path).

Docs:
- The Vercel AI SDK adapter now caches doStream in addition to doGenerate;
  move streaming out of "Known limitations" (only tool-call streams remain
  uncached, and cached streams replay as a single chunk).
@KIvanow KIvanow merged commit aa790ab into master Jul 7, 2026
3 checks passed
@KIvanow KIvanow deleted the chore/agent-cache-0.11.0 branch July 7, 2026 15:53
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 7, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant