You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Force LiteLLM OpenAI default to Responses; drop discovery tie-break
Revises the PR in two directions:
- `UiPathLiteLLM` now matches the langchain factory: when no `api_flavor`
is discovered or supplied for an OpenAI model, the client defaults to
`ApiFlavor.RESPONSES`. Existing `openai_*_client` test fixtures
that rely on previously-recorded chat-completions cassettes now pin
`api_flavor=CHAT_COMPLETIONS` explicitly; the
`openai_responses_client` fixture and `OPENAI_RESPONSES_CONFIGS`
continue to exercise Responses against their own cassettes.
- To keep OpenAI embeddings working under the new default, the LiteLLM
client's `embedding()` / `aembedding()` now pass the raw
`self._model_name` (no `responses/` / `invoke/` / `converse/` route
prefix) — those prefixes are completion-only.
- Drops the `get_model_info()` responses tie-break that was part of
the first commit. The LiteLLM default + langchain factory default
together cover the user-visible behavior; the tie-break was
redundant and narrowed the data model for a case already handled
by the defaults.
Related test updates:
- `test_openai_defaults_to_responses` replaces
`test_openai_defaults_to_chat_completions`; the litellm-model-name
assertion now expects the `responses/` prefix on the default path.
- Removes the three `get_model_info` tie-break tests added earlier.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,8 @@ All notable changes to `uipath_llm_client` (core package) will be documented in
5
5
## [1.9.3] - 2026-04-20
6
6
7
7
### Changed
8
-
-`UiPathBaseSettings.get_model_info()` now prefers the Responses API when discovery returns multiple OpenAI entries for the same model (both `chat-completions` and `responses` flavors present). The LiteLLM client keeps its `chat-completions` fallback for the single-entry / `apiFlavor=null` case because the same client serves embedding requests.
8
+
-`UiPathLiteLLM` now defaults to the OpenAI Responses API (`ApiFlavor.RESPONSES`) when discovery does not specify a flavor. Explicit `api_flavor=` and BYOM-discovered flavors still take precedence.
9
+
-`UiPathLiteLLM.embedding()` / `aembedding()` use the raw model name instead of `_litellm_model`. The `responses/` / `invoke/` / `converse/` route prefixes are completion-only, so this keeps OpenAI embeddings working when the client defaults to Responses on the completions side.
Copy file name to clipboardExpand all lines: packages/uipath_langchain_client/CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ All notable changes to `uipath_langchain_client` will be documented in this file
6
6
7
7
### Changed
8
8
-`get_chat_model()` now defaults to the OpenAI Responses API (`ApiFlavor.RESPONSES`) when discovery does not specify a flavor for an OpenAI chat model. Explicit `api_flavor=` on the call and BYOM-discovered flavors still take precedence.
9
-
- Minimum `uipath-llm-client` bumped to 1.9.3 for the `get_model_info()` Responses-preference tie-break.
9
+
- Minimum `uipath-llm-client` bumped to 1.9.3 to align with the matching LiteLLM default.
0 commit comments