agentic-flow 3.4.0 → 3.4.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +19 -0
- package/dist/.tsbuildinfo +1 -1
- package/dist/core/agentdb-fast.d.ts +9 -0
- package/dist/core/agentdb-fast.d.ts.map +1 -1
- package/dist/core/agentdb-fast.js +62 -31
- package/dist/core/agentdb-fast.js.map +1 -1
- package/dist/core/agentdb-filtered-search.d.ts +54 -0
- package/dist/core/agentdb-filtered-search.d.ts.map +1 -0
- package/dist/core/agentdb-filtered-search.js +111 -0
- package/dist/core/agentdb-filtered-search.js.map +1 -0
- package/dist/services/agentdb-service.d.ts +17 -0
- package/dist/services/agentdb-service.d.ts.map +1 -1
- package/dist/services/agentdb-service.js +55 -4
- package/dist/services/agentdb-service.js.map +1 -1
- package/package.json +3 -6
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,25 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
|
4
4
|
|
|
5
|
+
## [3.4.2] - 2026-11-08
|
|
6
|
+
|
|
7
|
+
### Fixed
|
|
8
|
+
- **`AgentDBFast` works again on agentdb 3.x.** Every `retrieveEpisodes`, `searchPatterns` and `getStats` call threw: agentdb's vector backends are async-only for search (`search is async-only. Use searchAsync()`), and `getStats` called a `stats()` method no backend has. Searches now go through `searchAsync` with agentdb's filtered search (`src/core/agentdb-filtered-search.ts`).
|
|
9
|
+
- **`AgentDBFast` filters are applied.** The `type` filter was dropped whenever it was the only predicate, so `retrieveEpisodes` returned patterns and `searchPatterns` returned episodes. `minReward`/`maxReward`/`minQuality` were sent as `$gte`/`$lte`, which agentdb's `FilterBuilder` does not know and silently ignores; they are now `$ge`/`$le`/`$range`. On the rvf backend (`@ruvector/rvf` 0.4.7) equality and ranges are filtered natively by field name; ruvector filters equality only, so ranges are applied after an over-fetch. If a filtered search throws, or a post-filtered answer comes back short, the search falls back to an exhaustive search filtered locally.
|
|
10
|
+
- `AgentDBFast` passes `vectorDimension` to agentdb (it passed `dimensions`, which agentdb ignores, so stores other than 384-d rejected every vector).
|
|
11
|
+
- `AgentDBFast.storeEpisode`/`storePattern` write through `insertAsync`, so an rvf metadata type clash rejects the call with agentdb's `RvfMetadataTypeConflictError` (now re-exported from `core/agentdb-fast`) instead of being parked in the backend's rejected-writes queue. `close()` awaits `closeAsync()` where the backend has it, so queued writes are flushed and the writer lock is released before it resolves.
|
|
12
|
+
- `AgentDBService.recallEpisodes` hands `minReward`/`reward: {$gte}`, `success`, `onlySuccesses`/`onlyFailures` and `timeWindowDays` to `ReflexionMemory.retrieveRelevant` instead of filtering an unfiltered result in JS; other keys still go through `MetadataFilter`. The in-memory fallback applies the same filters.
|
|
13
|
+
|
|
14
|
+
### Changed
|
|
15
|
+
- **`agentdb` `^3.0.0` → `^3.7.0`** (lockfile 3.0.0 → 3.7.0, `@ruvector/rvf` 0.4.7). `tests/integrations/agentdb37-filtered-search.test.ts` exercises the real package on the rvf and default backends: name-based filters, ranges, `forceExact`, `RvfMetadataTypeConflictError`, `closeAsync()`, and an `AgentDBService` round trip.
|
|
16
|
+
- `tests/integrations/no-workspace-protocol.test.ts` fails if a publishable `package.json` in the repo uses `workspace:`. The two examples that did are now `private` with real ranges; the non-existent `@agentic-flow/consensus-router` dependency is gone.
|
|
17
|
+
|
|
18
|
+
## [3.4.1] - 2026-11-06
|
|
19
|
+
|
|
20
|
+
### Changed
|
|
21
|
+
- **`aidefence` `^3.0.1` → `^3.0.2`.** aidefence 3.0.2 declares `zod ^4.6.7` itself, so the `overrides.aidefence.zod` entry added in 3.4.0 is removed. The lockfile still holds a single zod copy (4.6.7), and `aidefence/dist/detection` (the prompt-injection engine) loads and runs under it. `tests/mcp/zod4-migration.test.ts` now checks that aidefence resolves to the top-level zod 4 without an override.
|
|
22
|
+
- The optional `agent-booster` dependency (`^0.2.2`) also resolves the fixed 0.2.3, whose edits no longer fail when its WASM is rebuilt from source (see `packages/agent-booster/CHANGELOG.md`).
|
|
23
|
+
|
|
5
24
|
## [3.4.0] - 2026-11-06
|
|
6
25
|
|
|
7
26
|
Moves the package to zod 4. MCP clients see different default validation messages; see Changed.
|