Skip to content

v0.5.2 — documentation only

Choose a tag to compare

@andreab67 andreab67 released this 07 Sep 16:34
· 90 commits to main since this release
b9912f6

Documentation only — no redeploy needed

No code changes. git diff v0.5.1..v0.5.2 touches README.md, one test file, and the two version strings; the only change under hermes_pgvector/ is plugin.yaml's version string. An installed 0.5.2 behaves byte-for-byte like 0.5.1.

Why it exists

PyPI renders a project's README frozen at upload time, so two fixes that landed after v0.5.1 shipped were visible on GitHub but never on the package page:

  • The v0.5.1 release notes were out of order — the section sat before v0.5.0 instead of after it, burying the newest release mid-list. These sections run oldest-to-newest.
  • A test compared a failed count against a dry-run baseline that is hardcoded to 0, making the comparison a no-op — and its own commit message described it as a "delta", which wasn't true of the code.

Also fixes a review finding on that test: an inline comment cited the module docstring for a "THROWAWAY database" requirement the docstring didn't state. Rather than drop the citation, the requirement is now stated — it's real and was missing. Those backfill cases call backfill_null_embeddings(), which sweeps the whole table, so on a shared database they would stamp every pre-existing NULL-embedding row with the test's constant [0.1]*768 vector, after which a genuine backfill can never repair them.

Which version should you be on?

You are on Action
v0.5.1 Nothing — you already have every fix in this release
v0.5.0 or earlier Upgrade. v0.5.1 fixed a data-loss bug where a single memory remove deleted a whole theme's mirrored memory
pre-0.5.0 Upgrade, and note v0.5.0 renamed the import package — see its release notes for the one-time step

Validation

117 tests skip-mode, 164 against live Postgres 16 + pgvector 0.8.6. Attached artifacts are sha256-identical to the PyPI files.

Full changelog: v0.5.1...v0.5.2