You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Fix benchmark suite: 9 sites passing create_entity tuple as entity_id
(b1/b4/b5 had been broken since v0.2.2 when create_entity started
returning tuple[str, bool])
- Bump pytest>=9.0.3 (closes GHSA-6w46-j5rx-g56g, dev-time tmpdir)
- Add 'cortex' to ENTITY_STOPWORDS so the classifier stops extracting
the system's own name as a technology entity in self-referential
captures
- Hold litellm>=1.60 deliberately (inline comment in pyproject.toml):
bumping breaks 24 CLI tests via typer/click downgrades, and the
flagged litellm CVEs only affect litellm's proxy endpoints which
Cortex never starts.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [Unreleased]
9
9
10
+
## [0.3.5] — 2026-05-03
11
+
12
+
### Fixed
13
+
14
+
-**Benchmark suite restored** — `b1_hybrid_retrieval`, `b4_graph_intelligence`, `b5_pattern_detection` failed with `ValueError: Invalid IRI code point ' '` because they passed `store.create_entity(...)` (which returns `tuple[str, bool]`) directly as an entity ID. Updated 9 sites in `benchmarks/corpus/generator.py`, `benchmarks/b4_graph_intelligence/test_bench.py`, and `benchmarks/b5_pattern_detection/test_bench.py` to unpack the tuple.
15
+
16
+
### Changed
17
+
18
+
-**`pytest>=9.0.3`** (was `>=8.3`) — pytest 9 includes a compat shim for the `config.inicfg` private-attribute change; addresses dependency advisory GHSA-6w46-j5rx-g56g (dev-time tmpdir handling).
19
+
-**Entity classifier stopword list** — added `cortex` to `ENTITY_STOPWORDS` so the LLM no longer extracts the system's own name as a `technology` entity when users capture self-referential knowledge.
20
+
-**`litellm` constraint deliberately held at `>=1.60`** — see inline comment in `pyproject.toml`. The flagged litellm CVEs are in litellm's proxy server endpoints, which Cortex never starts (Cortex calls `litellm.completion()` as a library only). Bumping forces typer/click downgrades that break ~24 CLI tests, with no security benefit given Cortex's local-only deployment model.
0 commit comments