Release v4.6.0#155
Merged
Merged
Conversation
Removes the stale Roadmap.md gitignore entry (no such private file exists) so the public roadmap can live at the repo root.
Offline PII firewall for agent tool calls. Speaks the Claude Code hooks protocol: PreToolUse gates egress tools (ask/deny on EMAIL, PHONE, CREDIT_CARD, SSN findings), UserPromptSubmit and PostToolUse inject non-blocking warnings. Core-only dependencies, ~70ms per invocation, fail-open by design, never echoes matched PII in its own output.
docs: add public v5.0.0 roadmap
Offline PII guardrail for the LiteLLM proxy: pre_call redacts or blocks PII in request messages before egress, post_call redacts model responses. In-process, ~31µs per request — no sidecar service. Blocks surface as HTTP 400 guardrail interventions; engine errors follow a configurable fail policy (open/closed) and never leak matched text into logs or exception chains.
… coverage job Installs litellm in the nlp-advanced CI profile so the DataFogGuardrail tests execute where coverage thresholds are enforced, instead of being skipped and dragging patch coverage to zero.
feat: add Claude Code hook adapter (datafog-hook)
Base litellm does not include fastapi (it's in their proxy extra), so test collection failed with ModuleNotFoundError in CI. Proxy deployments always ship fastapi; CI now installs it alongside litellm and the test module skips gracefully without it. Adds edge-path tests (no-messages data, non-text content parts, opaque responses, observability failure) bringing the adapter to 100% line coverage.
feat: add LiteLLM guardrail adapter (DataFogGuardrail)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What ships in 4.6.0
A purely additive minor release: the two agent-firewall adapters, no changes to the core library or its dependencies.
datafog-hook) — offline PII firewall for agent tool calls (feat: add Claude Code hook adapter (datafog-hook) #152)DataFogGuardrail) — redact/block PII at the gateway for any provider (feat: add LiteLLM guardrail adapter (DataFogGuardrail) #154)See the CHANGELOG entry in this PR for full details.
Release mechanics
datafog/__about__.py(the stable pipeline publishes exactly this) and.bumpversion.cfg(was stale at 4.5.0b5)release_type=stablewithdry_run=true→ verify "Would have published: 4.6.0" →dry_run=false→ verify PyPI +v4.6.0tag → fast-forward dev to mainTest plan