Skip to content

feat(azure-open-ai): update model YAMLs [bot]#1019

Open
models-bot[bot] wants to merge 1 commit into
mainfrom
bot/update-azure-open-ai-20260513-111835
Open

feat(azure-open-ai): update model YAMLs [bot]#1019
models-bot[bot] wants to merge 1 commit into
mainfrom
bot/update-azure-open-ai-20260513-111835

Conversation

@models-bot
Copy link
Copy Markdown
Contributor

@models-bot models-bot Bot commented May 13, 2026

Auto-generated by poc-agent for provider azure-open-ai.


Note

Medium Risk
Broad config-only updates to Azure OpenAI model definitions (pricing/limits/status/modes) could affect model selection, availability filtering, and cost calculations if downstream consumers rely on these fields.

Overview
Refreshes the providers/azure-open-ai model catalog with serverless provisioning metadata added across most model YAMLs and multiple pricing/limits/source corrections.

Updates model lifecycle and compatibility metadata: several entries are now marked deprecated/retired with deprecationDate/isDeprecated, some models switch or add supportedModes (notably adding responses and changing certain models from chat to responses), and modalities are expanded for newer video/realtime/image models (e.g., adding image/video inputs or audio outputs).

Reviewed by Cursor Bugbot for commit 9fe012e. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions
Copy link
Copy Markdown
Contributor

/test-models

@harshiv-26
Copy link
Copy Markdown
Collaborator

Gateway test results

  • Total: 0
  • Passed: 0
  • Failed: 0
  • Validation failed: 0
  • Errored: 0
  • Skipped: 0
  • Success rate: 0.0%
Provider Model Scenarios

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 9fe012e. Configure here.

- prompt_caching
- structured_output
- system_messages
- tool_choice
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Contradictory tool_choice in features and removeParams

High Severity

tool_choice was added to features by this PR, but it already exists in removeParams. This is contradictory — the model advertises tool_choice support while simultaneously stripping that parameter from API requests. Every other model in the codebase has tool_choice in one list or the other, never both. The sibling model o3-deep-research-2025-06-26-ev3.yaml correctly has tool_choice only in removeParams with no corresponding feature entry.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 9fe012e. Configure here.

removeParams:
- response_format
- "n"
- n
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unquoted n parsed as boolean in YAML 1.1

Medium Severity

The quoted "n" in removeParams was changed to bare n in three files. In YAML 1.1 (used by tools like yamllint/PyYAML), bare n is interpreted as boolean false, not the string "n". The codebase convention is to quote it — the ModelParamKey type expects the string "n". While the project's js-yaml v4 (YAML 1.2) handles it correctly, this breaks consistency and portability.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 9fe012e. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant