Deepanshu 547535dbc5 feat(guardrails): add scan_raw_request flag so YAML order can't change enforcement ... Maintainer finding on BerriAI/litellm#34940: guardrails for the same hook run sequentially over one shared, progressively-mutated request dict, so declaring a masking guardrail before a blocking one hides the violation from it (200 vs 400 depending purely on YAML order). scan_raw_request opts a guardrail into always evaluating a snapshot taken before any guardrail in the hook ran, regardless of its declared position. Same contract as run_in_parallel: block-only, its own mutations discarded. Verified live: real proxy, real Gemini call, two custom guardrails (a redactor then a blocker). Same request, same declared order -- without the flag the blocker never sees the raw secret (200); with it, the blocker correctly rejects before any provider call (400).		2026-08-27 21:14:58 -04:00
..
helpers	test: require a match= on broad pytest.raises, and drop duplicate parametrize cases (#37769)	2026-08-20 20:24:49 -07:00
prisma_and_spend	Merge remote-tracking branch 'origin/litellm_internal_staging' into litellm_decrease_anys_opus5_round2	2026-08-25 16:17:29 -07:00
proxy_logging	feat(guardrails): add scan_raw_request flag so YAML order can't change enforcement	2026-08-27 21:14:58 -04:00
__init__.py	test(proxy/utils): pin bottom-of-file helper behavior (#29509)	2026-06-02 17:45:19 -07:00