Repository navigation
DataFog Core 1.6.0
DataFog Core 1.6.0 adds literal denylists and encrypted application vaults across the coordinated Core release. Workspace contract 1, marker syntax and existing snapshot formats remain unchanged.
Known EMAIL regression
EMAIL detection still misses punctuation-adjacent addresses in 1.6.0, including the four reproductions in MCP PR #82. For example, said "ok".alice@example.com returns no EMAIL finding, and 7|Reach carol@example.com.|alice@example.com omits the second address. These misses were reproduced against the published 1.6.0 wheel after release; this version does not resolve that regression. The correction tracked in Core #266 is merged in PR #267 and is being prepared for 1.7.0, which is not yet published. A dependency constraint below 1.7 will exclude that fix. MCP's adoption PR remains on hold pending the fix.
Changes
- Request-local literal deny rules across Rust, Python, Node.js and WASM, with explicit case sensitivity and word/substring boundaries. Deny rules take precedence over allowlists and saved not-sensitive choices.
- Python-first
datafog_fogvault.ApplicationVault: application-scoped encrypted storage, real OS credential providers or explicit external/file keys, cross-process locking, refreshed reads and durable compare-and-save before transformed text is returned. - Python
Workspace.prepare_forgetparity with Rust, Node and WASM, using existing snapshot v4 retirement semantics. Existing snapshots are not automatically rewritten; Core 1.0 cannot read v4. - Exact-release-commit qualification of real macOS Keychain, Windows Credential Manager and Linux Secret Service providers is now a publication requirement.
Coordinated packages
All 16 Core distributions use 1.6.0:
- PyPI:
datafog-core,datafog-fogvault. - crates.io:
datafog-core,datafog-fogvault-migration,datafog-fogvault-native. - npm:
@datafog/nodeand its five 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.6.0 datafog-fogvault==1.6.0
npm install --save-exact @datafog/node@1.6.0 @datafog/wasm@1.6.0
cargo add datafog-core@=1.6.0The independent FogVault engines and Python application datafog retain their own release tracks. Node application-helper support and extension/MCP denylist settings remain follow-ups.
Verification and boundaries
Release source: c266f79cb254605c5d2bf8be63913bda67dc062a.
All main CI workflows and twelve required installed-model checks passed on this source. One advisory Intel macOS model job failed its Python thread-progress timing assertion; the other two advisory jobs passed. Intel CI retirement is tracked separately in #263 and is not part of this release. Real-provider qualification covers fresh processes, synchronized writers, wrong/missing keys and cleanup; isolated macOS/Linux fixtures cover locked stores, and Linux verifies Secret Service restart against persisted keyring data. Machine reboot/new-login qualification remains deferred pending dedicated hosts. Consuming applications must validate their deployed executable identity, desktop prompt policy and code-signing/Keychain access policy.
Public registry archives were checked byte-for-byte against retained publication inputs. The attached SHA256SUMS covers all 28 distribution archives; publication-verification.json records the source, actual publication runs and registry checks. Python Core includes ten supported wheels plus its source distribution; its native companion includes three wheels. The 1.6.0 native Python companion Linux wheel requires glibc 2.38 or later (its manylinux_2_38_x86_64 tag is authoritative); this corrects the 2.34 minimum stated in its source README. The base Core Python Linux x64 wheel retains its separate manylinux 2.28 baseline.
See the release notes, literal denylist reference, and credential qualification scope.