[Bernd Verst (berndverst)]

Microsoft.Azure.DurableTask.ServiceBus 5.0.1

Fixes and improvements

• Corrected blob container listing and cleanup for task hub names containing dashes. Cleanup now distinguishes containers belonging to similarly named hubs, preventing cross-hub deletion. ([DurableTask.ServiceBus] Fix blob container listing and purge for hub names with dashes and culture-dependent container names #1424)
• Made blob container naming culture-invariant and protected containers created with legacy non-Gregorian calendar dates from incorrect expiration. ([DurableTask.ServiceBus] Fix blob container listing and purge for hub names with dashes and culture-dependent container names #1424)
• Session acceptance now honors the configured operation timeout, returning no session when the timeout expires. ([DurableTask.ServiceBus] Honor operationTimeout in SessionClient.AcceptMessageSessionAsync #1426)
• Added error logging for messages that do not fit in an outgoing batch. Diagnostics include the dropped message count, body size, destination, and batch capacity. This change reports dropped messages; it does not automatically retry them. ([DurableTask.ServiceBus] Log messages dropped by MessageSender.SendAsync when they don't fit in the batch #1425)
• Improved queue diagnostics to handle missing task hub queues without throwing an exception. ([DurableTask.ServiceBus] Fix blob container listing and purge for hub names with dashes and culture-dependent container names #1424)

Microsoft.Azure.DurableTask.Core changes

Updated Core from 3.10.0 to 3.11.2, including:

• Purge-orchestration version-check exemption: The specifically named BlobPurgeJobOrchestrator now bypasses worker version matching when its execution version is null or empty. Other orchestration names and nonempty versions retain their existing checks. This is a narrowly scoped exemption, not a configurable general exclusion. (Add opt-in version-check exclusions for unversioned orchestrations #1408)
• Entity state preservation: Fixed an extended-session processing case that could overwrite existing entity state with null when no worker result supplied replacement state. This affects Core's separate entity-dispatch path; it does not introduce entity support in the ServiceBus provider. (Fix extended sessions entities bug that could result in entity state deletion #1421)

[Copilot]

🔵 Needs a closer look

The new 1 MB Premium batch limit, combined with MessageSender skipping overflow messages, requires workload-level Service Bus integration testing to assess potential fan-out and tracking-message loss.

No open issues 🎉

What changed in this PR

Prepares DurableTask.ServiceBus 5.0.1 for release, packaging previously merged fixes with dependency updates while retaining the .NET Standard 2.0 target.

Changes:

• Bumps the ServiceBus package version from 5.0.0 to 5.0.1.
• Updates centrally managed Azure SDK, logging, JSON, diagnostics, and SourceLink dependencies.
• Broadens framework conditions to apply to .NET 8-compatible targets, including later .NET versions.

File	Description
test/​DurableTask.ServiceBus.Tests/​DurableTask.ServiceBus.Tests.csproj	Extends test dependencies and configuration copying to .NET 8-compatible targets.
src/​DurableTask.ServiceBus/​DurableTask.ServiceBus.csproj	Sets the ServiceBus package version to 5.0.1.
Directory.Packages.props	Updates shared dependency versions and broadens framework-specific conditions.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Core directly consumes Logging.Abstractions and DiagnosticSource 10.0.15, contradicting the documented 6.0.x patch updates and obscuring the compatibility impact of these major dependency upgrades.

1 open issue

• Release notes understate Core dependency upgrades · New

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

The version bump leaves central dependency versions unchanged, so the advertised SDK and other dependency upgrades are absent and must be applied or removed from the release description before publishing.

2 open issues

• Advertised dependency upgrades are missing from central package versions · New
• Release notes understate Core dependency upgrades

_{Review effort: Balanced}