1.0.0b2 (2026-11-13)
Features Added
- Added topic lifecycle operations (create or replace, list, get, update, and soft delete). Creation or replacement accepts
ChatTopicCreateOrReplace, which requirestitleand accepts optionalstatefor replacement; updates acceptChatTopicUpdate, whose fields are optional. - Added room, user, and user-room collection operations
Other Changes
- Changed the default service API version from
2026-02-01-previewto2026-08-01-previewfor both existing and newly added Chat operations - Clarified that message IDs are pagination cursors for
list_messages. The pager follows the service'snextLink; resume withby_page(continuation_token=...).
Breaking Changes
- Renamed request-body parameters from
resourcetorole,room,member,user,topic, ormessage, matching the operation's resource. Positional calls are unchanged. - Renamed
ChatConversation.parent_roomtoroom_id. The JSON field remainsparentRoom. - Removed the
continuation_token_parameterargument from listing operations. Resume paging withby_page(continuation_token=...)on the returnedItemPagedorAsyncItemPagedinstead. - Create or replace operations now accept dedicated
ChatRoleCreateOrReplace,ChatRoomCreateOrReplace,ChatRoomMemberCreateOrReplace, andChatUserCreateOrReplace(includingHumanChatUserCreateOrReplace) request models instead of resource response models. - Message updates accept
ChatMessageUpdate, whose fields are optional, instead ofChatMessage. Resource response model names are unchanged.