v1 voiceagents - #48312
Conversation
|
Azure Pipelines: Successfully started running 1 pipeline(s). 9 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
There was a problem hiding this comment.
Pull request overview
Regenerates the VoiceLive SDK model surface for the v1 Voice Agents API.
Changes:
- Reworks public models, enums, unions, and APIView mappings.
- Adds v1 audio, MCP, realtime, and RTC types.
- Updates package and generation metadata.
Reviewed changes
Copilot reviewed 7 out of 8 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
pyproject.toml |
Changes package classifier to Beta. |
models/_enums.py |
Replaces and expands protocol enums. |
models/__init__.py |
Updates public model exports. |
_utils/model_base.py |
Clarifies mapping-method documentation. |
_unions.py |
Defines new v1 model unions. |
apiview-properties.json |
Updates cross-language API mappings. |
_metadata.json |
Changes the generated API-version metadata. |
| RealtimeClientEventType, | ||
| RealtimeConversationItemMessageType, | ||
| RealtimeConversationItemType, | ||
| RealtimeServerEventType, |
| license = "MIT" | ||
| classifiers = [ | ||
| "Development Status :: 5 - Production/Stable", | ||
| "Development Status :: 4 - Beta", |
| class RealtimeServerEventType(str, Enum, metaclass=CaseInsensitiveEnumMeta): | ||
| """Type of RealtimeServerEventType.""" |
| ConversationRequestItem = Union[ | ||
| "_models.MessageItem", | ||
| "_models.FunctionCallItem", | ||
| "_models.FunctionCallOutputItem", | ||
| "_models.RealtimeMCPApprovalResponse", | ||
| ] |
[Pilot] PR Pipeline Failure AnalysisA CI pipeline failed on this pull request. Here is an automated analysis of what went wrong and how to get the build green. What failedThe
Root cause: The handwritten patch files ( Recommended next steps
Raw pipeline analysis (azsdk ci analyze)
|
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines