This release adds 5 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+14 more
Summary
AI summaryAdds five read‑only DuckDB UDFs for identity graph queries.
Full changelog
Identity Graph UDFs
Five new read-only DuckDB UDFs implementing the contract at docs/superpowers/specs/2026-05-12-identity-graph-duckdb-contract.md:
goldenmatch_identity_resolve(record_id, db_path)-> JSON viewgoldenmatch_identity_view(entity_id, db_path)-> JSON viewgoldenmatch_identity_history(entity_id, db_path)-> JSON event arraygoldenmatch_identity_conflicts(dataset, db_path)-> JSON edge arraygoldenmatch_identity_list(dataset, status, db_path)-> JSON identity list
Reads the SQLite (or Postgres) identity store maintained by the main goldenmatch package's pipeline. Same JSON shape across all surfaces (Python / REST / MCP / A2A / SQL).
Requires goldenmatch >= 1.15.0.
INSTALL <or pip install goldenmatch-duckdb>;
-- in Python:
import duckdb, goldenmatch_duckdb
con = duckdb.connect()
goldenmatch_duckdb.register(con)
con.sql("SELECT goldenmatch_identity_resolve('crm:abc-123', '.goldenmatch/identity.db')")
🤖 Generated with Claude Code
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About GoldenMatch
All releases →Related context
Related tools
Earlier breaking changes
- v3.1.0 `GOLDENMATCH_FRAME=polars` now requires the `[polars]` extra; raises error without it.
- vgoldencheck-v3.0.0 `inferred_type` emits neutral dtype vocabulary (str/int/uint/float/date/datetime/bool/other) instead of raw Polars dtypes.
- vgoldencheck-v3.0.0 'inferred_type' now emits a neutral dtype vocabulary instead of raw Polars dtype strings.
- vgoldencheck-v3.0.0 `scan_file`, `scan_dataframe`, and CLI `check` now run without Polars, using Arrow-native pyarrow.Table.
- v3.0.0 Result frames now return pyarrow.Table instead of Polars DataFrame.
Beta — feedback welcome: [email protected]