litellm/.github/workflows
Mateo Wang 9fbeebc988
feat(extraction): add /v1/extraction with Cloudflare Clairic support (#47473)
* feat(extraction): add Clairic extraction types and Cloudflare provider config

* feat(extraction): add the /v1/extraction route, router wiring, and Clairic billing

* fix(extraction): refuse or drop stream, pass unknown keys, run guardrails, keep the requested model name

Clairic does not stream, so stream=true answers 400 and is dropped and billed under drop_params. Keys LiteLLM does not know pass through to Cloudflare. Guardrails scan state, field instructions and text answers. Frozen decision and extraction responses now carry the requested model name. List fields must name their item type. /health/test_connection and the Add Model page accept the extraction mode.

* fix(extraction): keep upstream model names on decisions, scan images, keep typed values, refuse OpenAI params

Scope the frozen-response model stamp to extraction so /v1/decisions and /v1/systemone return the upstream name as on main. Pass request images to guardrails as data URLs and drop answer spans when a response guardrail rewrites state_text. Field spec values keep their JSON type, so a wrong type answers 400 instead of being coerced. OpenAI generation params answer 400 unless drop_params. The Model Hub shows a /v1/extraction snippet for extraction models.

* fix(extraction): send only Clairic's request fields, count extraction tokens, keep typed answers typed, drop spans a request guardrail made stale, and honor --max_tokens

* fix(extraction): scan number answers in response guardrails, rewrite guardrail fields in linear time, and leave --max_tokens as on main

* fix(extraction): scan float answers as whole numbers so fraction digits never trip a response guardrail

* fix(extraction): round only mean and median for response guardrails so fractional values keep their decimal text

* fix(extraction): count state and fields for budget reservations and scan estimate quantiles in response guardrails

* fix(extraction): send each repeated text to guardrails once and keep the context-window budget reservation

* test(extraction): type request_data in the guardrail test helpers
2026-10-20 15:51:45 -07:00
..
auto-close-duplicates.yml
auto_update_price_and_context_window.yml
check-schema-sync.yml
codeql.yml
codspeed.yml
compat-matrix-image.yml
conventional-commits.yml
cost-map-guard.yml
create-rc-branch.yml
create-release-branch.yml
deploy-dev-on-main.yml
duplicate_issue_check.yml
e2e_record_replay.yml
guard-fork-dependencies.yml
image-scan.yml
issue-keyword-labeler.yml
issue_classifier.yml
issue_fixed_comment.yml
issue_label_claude_code.yml
issue_label_sync.yml
lens-install-smoke.yml
linear-release.yml
mutation-test.yml
osv-scan.yml
publish-lint-base-counts.yml
scorecard.yml
stale.yml
sync-schema.yml
sync-together-ai-models.yml
test-e2e-redis-chaos.yml
test-linting.yml
test-mcp-dependency-resolution.yml
test-merge-smoke.yml
test-rust.yml
test-terraform-modules.yml
test-terraform-provider.yml
test-unit.yml
test-vscode-extension.yml
weekly_load_anomaly.yml
zizmor.yml