Skip to content

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

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

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

Conversation

@models-bot

@models-bot models-bot Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

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


Note

Medium Risk
Wide catalog changes affect routing, deprecation UX, and allowed API params; incorrect dates or param lists could mislead callers or break validation, but changes are declarative YAML only.

Overview
Bulk metadata refresh for azure-open-ai model YAMLs to match current Azure/OpenAI catalog and retirement schedules.

Deprecation: Sets isDeprecated: true on legacy chat/reasoning SKUs (e.g. gpt-4.1 / gpt-4.1-mini / gpt-4o variants, codex-mini, o4-mini).

Retirement dates: Updates retirementDate across chat, audio, image, embedding, and realtime models—often pushing dates later (e.g. many gpt-4.1/gpt-4o entries to 2027-04-14, embeddings to 2028-02-09).

Params & provisioning: Adds reasoning_effort (with supported values) and provisioning: serverless on some codex/GPT-5 entries; adjusts allowed reasoning_effort values on gpt-5.1 and gpt-5.1-codex-max; removes reasoning_effort from gpt-5.3-codex-2026-02-24; drops sources from gpt-5-nano.

New/expanded model: gpt-offline-whisper-1-2026-07-27 is defined as audio_transcription (was effectively stub/unknown) with modalities and serverless provisioning.

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

@github-actions

github-actions Bot commented Aug 8, 2026

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

@cursor cursor Bot left a comment

Copy link
Copy Markdown

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 using default effort 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 a3bebaf. Configure here.

removeParams:
- reasoning_effort
retirementDate: "2026-10-01"
retirementDate: "2027-04-14"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Wrong gpt-4o retirement dates

High Severity

retirementDate was changed to 2027-04-14 for gpt-4o-2024-11-20 and gpt-4o-mini, but Azure's schedule keeps these models retiring on 2026-10-01. That date matches gpt-4.1 instead, so migration timelines based on this registry would be about six months too late and risk production failures after retirement.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit a3bebaf. Configure here.

- max_tokens
- reasoning_effort
retirementDate: "2027-04-15"
retirementDate: "2028-02-09"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Wrong ada-002 retirement dates

High Severity

retirementDate for text-embedding-ada-002 and text-embedding-ada-002-2 was changed from 2027-04-15 to 2028-02-09. Azure still lists ada-002 versions as retiring on April 15, 2027; 2028-02-09 appears to be the text-embedding-3-large date applied to the wrong models.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit a3bebaf. Configure here.

- structured_output
- system_messages
- tool_choice
isDeprecated: true

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

need to fix these

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.

2 participants