ryan-crabbe-berri fe480533e8 feat(proxy)!: refuse to start with an unset, empty, or publicly known master key ... The proxy used to boot with no master key (every request accepted without authentication) and with sk-1234, the key every example used. It now stops at startup, before it connects to the database, and prints how to fix it: where the bad key came from, a copy-pastable command that generates a secure key, and, when the public key is also encrypting a database, a link to the rotation guide general_settings.dangerously_allow_unsafe_proxy: true or LITELLM_DANGEROUSLY_ALLOW_UNSAFE_PROXY=true starts the proxy anyway, for local development. CI and test boots that rely on sk-1234 or on no key set it BREAKING CHANGE: deployments with no master key, an empty one, or sk-1234 no longer start until they set a real key or opt in to the override		2026-09-19 13:44:00 -07:00
..
auth	test(auth): freeze prefetch cache clock so the org getter cannot miss on a slow runner	2026-09-14 18:13:49 +00:00
management	feat(proxy)!: refuse to start with an unset, empty, or publicly known master key	2026-09-19 13:44:00 -07:00
spend	fix(proxy): attribute gate-rejected requests to their endpoint in cache analytics (#40824)	2026-09-12 16:03:38 -07:00
__init__.py	feat(tests): behavior-pinning harness + Key Tier-1 matrix (#28321)	2026-05-20 19:27:44 -07:00