fix(uipath-core): accept minimal conversation message envelope on input#1677
Merged
Merged
Conversation
github-actions
Bot
added
test:uipath-langchain
There was a problem hiding this comment.
Pull request overview
This PR updates the uipath-core conversation Pydantic models to accept minimal inbound message payloads by making server-allocated fields optional and providing sensible defaults for list fields, aligning model validation with the Conversational Agent Service contract.
Changes:
- Made
createdAt/updatedAtoptional onUiPathConversationMessageandUiPathConversationContentPart. - Defaulted
toolCallsandcitationsto empty lists to allow omission in inbound payloads. - Added a unit test to pin minimal inbound message validation behavior; bumped
uipath-coreversion to0.5.16and updated lockfiles accordingly.
Reviewed changes
Copilot reviewed 4 out of 8 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| packages/uipath/uv.lock | Updates lock metadata and bumps editable uipath-core to 0.5.16. |
| packages/uipath-platform/uv.lock | Updates lock metadata and bumps editable uipath-core to 0.5.16. |
| packages/uipath-core/uv.lock | Updates lock metadata and bumps uipath-core to 0.5.16. |
| packages/uipath-core/tests/chat/test_message.py | Adds regression test ensuring minimal inbound user message payload validates and defaults are applied. |
| packages/uipath-core/src/uipath/core/chat/message.py | Makes message timestamps optional and defaults toolCalls to []. |
| packages/uipath-core/src/uipath/core/chat/content.py | Makes content-part timestamps optional and defaults citations to []. |
| packages/uipath-core/pyproject.toml | Bumps uipath-core version from 0.5.15 to 0.5.16. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
GabrielVasilescu04
approved these changes
May 22, 2026
radu-mocanu
force-pushed
the
fix/conversation-message-optional-fields
branch
from
ef3f930 to
90dbf85
Compare
radu-mocanu
changed the title
radu-mocanu
force-pushed
the
fix/conversation-message-optional-fields
branch
from
90dbf85 to
346adca
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
messageId/contentPartIddefault tostr(uuid.uuid4())if absent on input (same UUIDs thatuipath devinjects server-side, just moved into the model)createdAt,updatedAtnow optional;toolCallsandcitationsdefault to[]{"role": "user", "contentParts": [{"mimeType": "text/plain", "data": {"inline": "..."}}]}now validates againstUiPathConversationMessageWhy
matches the CAS contract