What
The v0.2.0 tag exists on GitHub and on crates.io (vecq-core 0.2.0), but CHANGELOG.md at the tag (and on main) still tops out at 0.1.1. The release includes significant user-facing changes (keyed API + tombstones #16, AVX2 path #17, SQLite BLOB docs #18) that are invisible to anyone reading the changelog.
Suggestion
Add a ## [0.2.0] — 2026-08-28 section (Added: keyed API add_keyed/remove_keyed/compact/search_keyed; Added: AVX2 scoring path with bit-identity tests; Docs: SQLite BLOB pattern) and consider making "CHANGELOG entry" part of the release checklist so the tag can't fly without it (same class of guard we just learned to add on cora-code after a mis-tagged release).
What
The
v0.2.0tag exists on GitHub and on crates.io (vecq-core 0.2.0), butCHANGELOG.mdat the tag (and onmain) still tops out at0.1.1. The release includes significant user-facing changes (keyed API + tombstones #16, AVX2 path #17, SQLite BLOB docs #18) that are invisible to anyone reading the changelog.Suggestion
Add a
## [0.2.0] — 2026-08-28section (Added: keyed APIadd_keyed/remove_keyed/compact/search_keyed; Added: AVX2 scoring path with bit-identity tests; Docs: SQLite BLOB pattern) and consider making "CHANGELOG entry" part of the release checklist so the tag can't fly without it (same class of guard we just learned to add on cora-code after a mis-tagged release).