Repository navigation
DataFog Core 1.7.0 restores EMAIL and PHONE findings that 1.5.0 and 1.6.0 miss, and retires Intel macOS prebuilt packages. Workspace contract 1, marker syntax and existing snapshot formats are unchanged from 1.6.0.
Fixed detection regressions
Core 1.5.0 and 1.6.0 drop values that 1.4.0 reported (#266). 1.7.0 includes the fixes in #267 and #270. A dependency constraint below 1.7 excludes these fixes.
- EMAIL after surrounding punctuation and delimiters.
said "ok".alice@example.comandcarol@example.com.|alice@example.comreport every address. - EMAIL directly after one or more dots, in text, ENV and SQL formats:
see [1].alice@example.com,me...alice@example.comandKEY=".alice@example.com"reportalice@example.com. This replaces the 1.5.0 malformed-local rejection:bob..x@example.comis reported asx@example.com, and the text before the dots is not covered by the span. - PHONE after a digit and a separator. CSV rows with a numeric column are found again:
2,+1-202-555-0143,1,34,2025550143, every number in2025550143,2025550144, and7,+1.2025550143. After a digit and dot, a candidate with+, parentheses or another separator is reported. - PHONE is matched on each line separately, so a number at a line end is no longer dropped when the next line starts with a digit.
Accepted false positives, as in 1.4.0: a decimal-comma value with exactly ten fractional digits that pass validation (or eleven starting with 1), a ten-digit integer after another numeric column, and a +-signed decimal after a numeric column. Still not reported: an unsigned single-dot decimal after a digit and comma (6,306.2723362, which also rejects 2,202.5550143), and unseparated or dotted runs directly after a digit and dot (2.202.555.0143), a remaining difference from 1.4.0. Digit groups separated by VT, FF, NEL, U+2028 or U+2029 are no longer joined into one number. The changelog has the exact rules.
Other changes
- Intel macOS is retired from qualification and prebuilt publication (#264). Python omits its Intel macOS wheel and Node omits
@datafog/node-darwin-x64. Existing 1.6.0 Intel archives remain available. - The Linux x64 wheel of the native Python companion
datafog-fogvaultrequires glibc 2.38 or later (manylinux_2_38_x86_64); basedatafog-coreGNU wheels keep their glibc 2.28 baseline.
Coordinated packages
All 15 Core distributions use 1.7.0:
- PyPI:
datafog-core,datafog-fogvault. - crates.io:
datafog-core,datafog-fogvault-migration,datafog-fogvault-native. - npm:
@datafog/nodeand its four native platform packages,@datafog/wasm,@datafog/core-fogvault-browser,@datafog/core-fogvault-legacy-browser,@datafog/core-sqlite-browser,@datafog/core-fogvault-node.
python -m pip install datafog-core==1.7.0 datafog-fogvault==1.7.0
npm install --save-exact @datafog/node@1.7.0 @datafog/wasm@1.7.0
cargo add datafog-core@=1.7.0The independent FogVault engines and the Python application datafog keep their own release tracks.
Verification and boundaries
Release source: 56f4d311737e2a245cdbd01ed11e54c3e87bb4dd.
The exact-commit Core/FogVault gate and the twelve required installed-model checks passed on this source. One model job (gliner2, macOS) failed a Python thread-progress timing assertion on its first attempt and passed on a single re-run; the same assertion passed in the two other macOS model jobs. The dependency advisory scan fails on RUSTSEC-2026-0543 (chrono unmaintained), which affects only the internal xtask tool and no published package; tracked in #271.
The detection fixes were reviewed in two independent passes with separately written generators and compared against published 1.4.0 and 1.6.0: no EMAIL finding of the previous main is lost or re-spanned, and no PHONE or EMAIL finding is reported that neither 1.4.0 nor the previous main reports, apart from numbers at a line end that 1.4.0 joined to the next line. After publication, the published datafog-core 1.7.0 wheel was installed from PyPI and reproduced the fixed cases.
The publication workflows admit only archives from the qualifying exact-commit runs. After publication, all 26 public archives were downloaded and their digests matched the registry records; the attached SHA256SUMS lists them. Python Core has nine wheels plus its source distribution; the native Python companion has three wheels.
See the release notes.