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
Feat: use _UNSET sentinel to exclude unset UiPathChat params from payload
`UiPathChat` parameter fields now default to an internal `_UNSET`
singleton instead of `None`, and `_default_params` filters on the
sentinel rather than on `None`.
Behavior change: passing an explicit `None` (e.g. `UiPathChat(
temperature=None)`) now forwards `null` to the normalized API instead
of being silently dropped. Unset fields continue to be omitted.
Callers relying on `None` as shorthand for "omit" should stop passing
the argument.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: packages/uipath_langchain_client/CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,11 @@
2
2
3
3
All notable changes to `uipath_langchain_client` will be documented in this file.
4
4
5
+
## [1.9.7] - 2026-04-22
6
+
7
+
### Changed
8
+
-**Behavior change:**`UiPathChat` parameter fields now default to an internal `_UNSET` sentinel instead of `None`, and `_default_params` filters on the sentinel rather than on `None`. Unset fields are still omitted from the request payload, but passing an explicit `None` (e.g. `UiPathChat(temperature=None)`) now forwards `null` to the normalized API instead of being silently dropped. Previously, both "not passed" and "explicitly `None`" produced the same omission. Callers relying on `None` as shorthand for "omit" should switch to simply not passing the argument.
0 commit comments