Skip to content

GoldenMatch

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

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

Published 12d 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 12d

The release updates minimum runtime versions: goldenmatch[polars] to >=3.3 and goldenmatch-native to >=0.1.15.

Why it matters: Projects depending on goldenmatch must ensure their builds use polars version 3.3 or higher and native version 0.1.15 or higher; failure triggers runtime failures.

Summary

AI summary

Minimum runtime versions bumped to goldenmatch[polars]>=3.3 and goldenmatch-native>=0.1.15.

Changes in this release

Dependency Medium

Bump goldenmatch[polars] dependency to version >=3.3.

Bump goldenmatch[polars] dependency to version >=3.3.

Source: llm_adapter@2026-07-15

Confidence: high

Dependency Medium

Bump goldenmatch-native dependency to version >=0.1.15.

Bump goldenmatch-native dependency to version >=0.1.15.

Source: llm_adapter@2026-07-15

Confidence: high

Full changelog

Floor bump: goldenmatch[polars]>=3.3 (FS negative evidence on probabilistic matchkeys, Splink migration upgrade pass incl. the fan-out/NE lever) and goldenmatch-native>=0.1.15 (native FS negative evidence + fused N-level banding, FS_SUPPORTS_NE).

Breaking Changes

  • Minimum required version of goldenmatch[polars] raised to 3.3 (introduces FS negative evidence on probabilistic matchkeys and Splink migration upgrade pass).
  • Minimum required version of goldenmatch-native raised to 0.1.15 (adds native FS negative evidence, fused N-level banding, and FS_SUPPORTS_NE support).

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

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]