GoldenMatch

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

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 16d Data Pipelines & ETL

View tool

✓ 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 golden‑suite release v0.1.10 updates the minimum required goldencheck version to 2.0.0 and adds a `[polars]` extra dependency.

Why it matters: Projects using golden-suite must ensure their build configurations include the polars extra when upgrading goldencheck ≥2.0.0; otherwise builds will fail due to missing optional dependencies.

Summary

AI summary

Bumped minimum goldencheck version to 2.0.0 with [polars] extra requirement.

Changes in this release

Type	Severity	Summary	CVE
Dependency	Low	Bumped goldencheck minimum version to 2.0.0 with [polars] extra requirement. Bumped goldencheck minimum version to 2.0.0 with [polars] extra requirement. Source: llm_adapter@2026-07-15 Confidence: high	—
Dependency	Low	Updated goldencheck floor to >=2.0.0[polars]. Updated goldencheck floor to >=2.0.0[polars]. Source: granite4.1:30b@2026-07-15-audit Confidence: low	—

Full changelog

golden-suite 0.1.10

Lockstep bump after goldencheck 2.0.0 (Polars eviction).

Bumped the goldencheck floor to goldencheck[polars]>=2.0.0 (was >=1.4.1). goldencheck 2.0.0 moved Polars from a base dependency to the [polars] extra; the [polars] marker keeps CSV reading and the full scan_file/scan_dataframe scan working in a suite install. Parquet/Excel reading and the structural scan_columns checks run Polars-free.

The suite already pulls Polars via goldenmatch, so this is the explicit declaration; runtime is unchanged.

Breaking Changes

Minimum goldencheck version increased to >=2.0.0 with `[polars]` extra required

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.

About GoldenMatch

All releases →

Related context

Related tools

vector

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.