Azure/azure-sdk-for-go sdk/data/azcosmos/v1.5.0-beta.6 on GitHub

1.5.0-beta.6 (2026-05-15)

Adds PriorityLevel and ThroughputBucket options at the client and per-request level for item, query, change-feed, batch, and read-many operations. See PR 26750
Added client-level partition key range cache and container properties cache, reducing redundant metadata round-trips for ReadMany and query operations. See PR 26723
Added operation diagnostics on responses and DiagnosticsFromError for retrieving diagnostics from failed operations. See PR 26548

Removed ChangeFeedResponse.PopulateCompositeContinuationToken(). The method is no longer needed: GetChangeFeed now populates ChangeFeedResponse.ContinuationToken directly with the multi-range composite token. Callers who built single-range tokens manually can use GetCompositeContinuationToken() instead. See PR 26792.

Fixed GetChangeFeed to survive partition splits: customer-supplied FeedRanges are now overlap-matched against the routing map, 410/Gone triggers a cache refresh and bounded retry, split parents expand into per-child queue entries (inheriting the parent's ETag), and the continuation token persists multi-range state across calls. Continuation tokens are guarded against cross-container reuse. See PR 26768.
Fixed V2 partition key routing: the top 2 bits of the first EPK byte are now masked to stay within the partition key range space [0x00, 0x3F]. Previously, items whose V2 hash started with a byte >= 0x40 could fail routing in ReadMany because the EPK lexicographically exceeded the "FF" range sentinel. See PR 26723
Fixed error handling for partition key range calls which would previously cause panics on any error. See PR 26723
Fixed partition key range cache to use change-feed pagination when fetching ranges, preventing incomplete range sets on containers with many partitions. The incremental refresh path now accumulates all pages before merging, correctly handling cascading splits across multiple change-feed pages. See PR 26777