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
{{ message }}
Repository navigation
Commit 9b082b3
Browse filesBrowse the repository at this point in the historyBrowse files
* test: a 0.1.0 database upgrades with no data loss
Migrates and writes a database with the published 0.1.0 package, then
runs this version's migrations and checks every row survives and the
0.1.0 documents stay searchable.
* test: move the real-Postgres suites to e2e/
The end-to-end suites and their harness move from tests/ to the root
e2e/ directory, with the database harness and HTTP stub merged into
e2e/helpers.ts, to match the repo test layout. bun run test now runs
src/ only and the new test:e2e script runs e2e/; CI runs both.
* chore(release): 0.2.0
derived_from, …). `memory_feed` tool. Feed entries include `accessTags`.
177
-
See `docs/DISTILLER.md`
178
-
179
-
### Removed
180
-
181
-
- Host-injected generate path on the plane (use host inference + `add` / `search`)
182
-
183
-
## [0.1.2] — 2026-07-31
184
-
185
-
### Added
186
-
- Public `createMemory` export for out-of-band capture and search (CLI seeders, batch ingesters, tests) without mounting HTTP routes (`#8`)
187
-
188
-
### Fixed
189
-
190
-
- Fail-closed document ACL: withhold hits whose `acl_block` is unreadable or non-string (`#9`)
191
-
- Timeline titles use the same document ACL post-filter as search (`#12`)
192
-
- Return 401 (not 500) when the host has not resolved a principal (`#7`)
193
-
- ACL wiring tests mock `sql.unsafe` for FTS verification so the suite stays green under the search path
194
-
195
-
## [0.1.1] — 2026-07-31
196
-
197
-
### Added
198
-
199
-
- Halfvec expression indexes for embedding models above 2000 dimensions (up to 4000); dense search ORDER BY uses the same expression as the index (`#1`)
200
-
- Configurable lexical FTS language (`FTS_LANGUAGE` / `EngineConfig.ftsLanguage`) with parse, catalog verify, and rebuild recipe; public `DEFAULT_FTS_LANGUAGE` export (`#4`)
201
-
- Named chunk FK with `ON DELETE CASCADE` and composite tenant index on per-model embedding tables created at activation (`#3`)
202
-
203
-
### Changed
204
-
205
-
- Dense search scales `hnsw.ef_search` to the overfetch limit (floor 40) and probes `hnsw.iterative_scan = relaxed_order` once per process when available (`#2`)
206
-
- Package install docs point at `@corbits/memory` (`#6`)
207
-
208
-
### Fixed
209
39
210
-
- Rerank document truncation to fit cross-encoder token limits (`#10`)
211
-
- Degrade metrics: surface full rerank failure detail and count DegradeFlags so silent degradation is visible (`#11`)
40
+
### Upgrading from 0.1.0
212
41
213
-
## [0.1.0] — 2026-07
42
+
- Call the new `runMemoryMigrations` once; it upgrades a 0.1.0 database in
43
+
place with no data loss.
44
+
- After the upgrade, do not run 0.1.0 against the database: its ledger is
- No issue-tracker ticket references (e.g. `CL-1234`) in commit messages,
61
-
code, or comments — commit messages should be self-explanatory without an
62
-
external ticket.
63
-
- One logical change per commit where practical; a commit message describes
64
-
the change, not the task that produced it.
65
-
66
56
## Contributor License Agreement
67
57
68
58
Contributions require agreeing to the project's CLA — see `CLA.md`. The CLA
69
59
bot will comment on your first PR with instructions if you haven't signed
70
60
yet.
61
+
62
+
## Commit messages
63
+
64
+
Commit subjects and PR titles follow [Conventional Commits](https://www.conventionalcommits.org): `feat`, `fix`, `refactor`, `test`, `docs`, `build`, `ci`, `perf`, and `chore(release): x.y.z` for releases.
65
+
Add `!` only for public API breaks: removed or renamed exports, changed signatures, newly required params. Peer and dependency range changes are `build(deps):` with no `!`.
66
+
Keep subjects imperative, lowercase after the colon, 72 characters or less, and free of ticket IDs.
67
+
No ticket IDs in code or comments either. One logical change per commit where practical; describe the change, not the task that produced it.
68
+
Every PR links its issue with a `Closes <issue id>` line in the PR body.
0 commit comments