From b501b94d6a4bb27b6f54f0113f18bcd3b218c987 Mon Sep 17 00:00:00 2001
From: samtsai15 <6171228+samtsai15@users.noreply.github.com>
Date: Fri, 28 Aug 2026 16:15:29 +0800
Subject: [PATCH] chore: regenerate the OpenAPI snapshot and dashboard types
 for on_unscannable_image

`on_unscannable_image` lives on BedrockGuardrailConfigModel, so it surfaces in the
proxy's OpenAPI schema, and two generated files that are committed to the repo
have to carry it: the lazy-route snapshot /openapi.json serves for unloaded
features, and the dashboard's schema.d.ts.

This passed before the merge. The base regenerated the snapshot without this
branch in it, so the field went missing and the check caught it -- the same
"a new base moves the baseline" shape as the LIT010, reportArgumentType and C901
failures earlier in this PR.

Both files are regenerated by the documented commands rather than hand-edited,
since CI regenerates and diffs them. package-lock.json picked up unrelated churn
from the local npm install and has been left alone.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---
 litellm/proxy/_lazy_openapi_snapshot.json     | 10 ++++++++++
 ui/litellm-dashboard/src/lib/http/schema.d.ts |  7 +++++++
 2 files changed, 17 insertions(+)

diff --git a/litellm/proxy/_lazy_openapi_snapshot.json b/litellm/proxy/_lazy_openapi_snapshot.json
index c75eaa60fcf..70de9903ee1 100644
--- a/litellm/proxy/_lazy_openapi_snapshot.json
+++ b/litellm/proxy/_lazy_openapi_snapshot.json
@@ -11119,6 +11119,16 @@
               "description": "Action to take when sensitive data is detected. 'block' raises an exception (default behavior). 'route' reroutes the request to the model specified in sensitive_data_route_to_model.",
               "title": "On Sensitive Data"
             },
+            "on_unscannable_image": {
+              "default": "block",
+              "description": "What to do with an image the guardrail cannot scan - ApplyGuardrail accepts png/jpeg only, and remote image URLs are not fetched while litellm.user_url_validation is disabled. 'block' (default) rejects the request; 'allow' logs a warning and sends the image to the model unscanned.",
+              "enum": [
+                "block",
+                "allow"
+              ],
+              "title": "On Unscannable Image",
+              "type": "string"
+            },
             "on_violation": {
               "anyOf": [
                 {
diff --git a/ui/litellm-dashboard/src/lib/http/schema.d.ts b/ui/litellm-dashboard/src/lib/http/schema.d.ts
index 1e1ce665970..3cd5c89d957 100644
--- a/ui/litellm-dashboard/src/lib/http/schema.d.ts
+++ b/ui/litellm-dashboard/src/lib/http/schema.d.ts
@@ -29882,6 +29882,13 @@ export interface components {
              * @description Action to take when sensitive data is detected. 'block' raises an exception (default behavior). 'route' reroutes the request to the model specified in sensitive_data_route_to_model.
              */
             on_sensitive_data?: ("block" | "route") | null;
+            /**
+             * On Unscannable Image
+             * @description What to do with an image the guardrail cannot scan - ApplyGuardrail accepts png/jpeg only, and remote image URLs are not fetched while litellm.user_url_validation is disabled. 'block' (default) rejects the request; 'allow' logs a warning and sends the image to the model unscanned.
+             * @default block
+             * @enum {string}
+             */
+            on_unscannable_image: "block" | "allow";
             /**
              * On Violation
              * @description For /v1/realtime sessions: 'warn' speaks the violation message and continues; 'end_session' speaks the message and closes the connection.