litellm/backend
Tin Chi Lo 6e0290011f fix(spend): register the benchmarks route and the session rollup's retention
Three CI gates caught the same class of omission: this PR adds a new member to
an enumerated set, and each set has a registry or a test that enumerates it.

The benchmarks route was reachable on the monolithic app but present in neither
component allowlist, so it would have 404'd on both the gateway and the backend
pod. It is an admin read over the rollup, so it belongs on the backend, next to
the adaptive-router routes it sits beside in the dashboard.

The retention cleanup gained a fourth table, which moved two call counts the
spend-log cleanup tests assert on. Those tests now also assert that the new
table is actually pruned and that it is keyed on last activity, so the count is
backed by a claim about behaviour rather than standing alone.

The rollup's cleanup log line built its message eagerly instead of passing the
count as a %-style argument
2026-08-04 13:39:20 -07:00
..
routes fix(spend): register the benchmarks route and the session rollup's retention 2026-08-04 13:39:20 -07:00
Dockerfile fix(docker): honor USE_DDTRACE in the componentized gateway and backend images (#35490) 2026-08-01 14:12:59 -07:00
main.py chore(oss): litellm oss staging 120626 (#30292) 2026-06-12 09:49:25 -07:00