Skip to content

GoldenMatch

vgolden-suite-v0.3.1 scope: golden-suite Breaking

This release includes 2 breaking changes for platform teams planning a safe upgrade.

Published 8d Data Pipelines & ETL
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

data-cleaning data-engineering data-matching data-quality deduplication entity-resolution
+14 more
fellegi-sunter fuzzy-matching knowledge-graph llm master-data-management mcp-server polars pprl python record-linkage rust splink typescript zero-config

ReleasePort's take

Light signal
editorial:auto 8d

The golden-suite release v0.3.1 raises the minimum required versions to goldenmatch >= 3.5 and goldenmatch‑native >= 0.1.18.

Why it matters: Projects using goldenmatch must update dependencies to version 3.5 or higher and add goldenmatch‑native ≥ 0.1.18; failure results in incompatibility with the new suite release.

Summary

AI summary

Minimum version bumps for goldenmatch and goldenmatch‑native to 3.5 and 0.1.18 respectively.

Changes in this release

Feature Medium

Add native date_similarity kernel via goldenmatch-native >=0.1.18

Add native date_similarity kernel via goldenmatch-native >=0.1.18

Source: llm_adapter@2026-07-19

Confidence: high

 —
Dependency Medium

Upgrade goldenmatch[polars] from >=3.4 to >=3.5

Upgrade goldenmatch[polars] from >=3.4 to >=3.5

Source: llm_adapter@2026-07-19

Confidence: high

 —
Full changelog

golden-suite 0.3.1 -- lockstep floor bump after the goldenmatch 3.5.0 train.

  • goldenmatch[polars] >=3.4 -> >=3.5: the date-aware date scorer; the FS
    missing-value correctness wave that restored historical_50k probabilistic F1
    0.33 -> 0.83; 100% native Fellegi-Sunter coverage via the shared fs-core
    crate; and the from_splink random-pair-prior fix.
  • goldenmatch-native >=0.1.17 -> >=0.1.18: adds the native date_similarity
    kernel so the date scorer runs on the native path, not just the pure-Python
    fallback.

Cut after goldenmatch 3.5.0 + goldenmatch-native 0.1.18 landed on PyPI
(member-on-PyPI-first lockstep).

Breaking Changes

  • Minimum goldenmatch version raised from >=3.4 to >=3.5.
  • Minimum goldenmatch‑native version raised from >=0.1.17 to >=0.1.18.
View diff on GitHub

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

Share on X Share on Bluesky

Track GoldenMatch

Get notified when new releases ship.

Sign up free

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]