fix(chatmodels): add newer Azure OpenAI models#6414
Conversation
There was a problem hiding this comment.
Code Review
This pull request adds several GPT-5.x models, including gpt-5.5 and gpt-5.4 variants, to the Azure ChatOpenAI provider within the models configuration. Additionally, a new test suite has been introduced to ensure that these Azure models are correctly aligned with the standard ChatOpenAI provider entries. I have no feedback to provide.
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds newer GPT-5.x model entries to the azureChatOpenAI provider and introduces a regression test to ensure Azure’s registry stays aligned with the chatOpenAI model definitions.
Changes:
- Add GPT-5.5 / GPT-5.4 variants to
azureChatOpenAIinmodels.json - Add a test that checks GPT-5.x Azure entries match corresponding
chatOpenAIentries
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| packages/components/src/modelRegistry.test.ts | Adds a Jest test asserting Azure ChatOpenAI GPT-5.x models match ChatOpenAI definitions |
| packages/components/models.json | Adds GPT-5.5 and GPT-5.4* model entries to the azureChatOpenAI provider |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
Closes #6411.
Validation
node -e "const m=require('./packages/components/models.json'); const names=['gpt-5.5','gpt-5.5-pro','gpt-5.4','gpt-5.4-pro','gpt-5.4-mini','gpt-5.4-nano']; const azure=m.chat.find(p=>p.name==='azureChatOpenAI').models; const open=m.chat.find(p=>p.name==='chatOpenAI').models; for (const n of names) { const a=azure.find(x=>x.name===n); const o=open.find(x=>x.name===n); if (JSON.stringify(a)!==JSON.stringify(o)) throw new Error(n); } console.log('azure model parity ok')"git diff --checkpnpm exec prettier --check packages/components/models.json packages/components/src/modelRegistry.test.tsNODE_OPTIONS=--max-old-space-size=4096 pnpm --filter flowise-components test -- modelRegistry.test.ts --runInBandNote: the first focused Jest attempt hit the default Node heap limit locally; rerunning the same focused suite with a 4096 MB heap completed successfully.