Bump the azure group with 1 update - #3346
Merged
mergify[bot] merged 1 commit intoSep 25, 2026
Merged
mergify[bot] merged 1 commit into
mergify[bot] merged 1 commit into
Conversation
Bumps Azure.Messaging.ServiceBus from 7.20.2 to 7.21.0 --- updated-dependencies: - dependency-name: Azure.Messaging.ServiceBus dependency-version: 7.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: azure ... Signed-off-by: dependabot[bot] <support@github.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3346 +/- ##
=======================================
Coverage 30.95% 30.95%
=======================================
Files 41 41
Lines 743 743
Branches 21 21
=======================================
Hits 230 230
Misses 509 509
Partials 4 4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
dependabot
Bot
deleted the
dependabot/nuget/BervProject.WebApi.Boilerplate/azure-daa646b83c
branch
September 25, 2026 01:10
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.



Updated Azure.Messaging.ServiceBus from 7.20.2 to 7.21.0.
Release notes
Sourced from Azure.Messaging.ServiceBus's releases.
7.21.0
7.21.0 (2026-10-06)
Features Added
SqlFilterCountandCorrelationFilterCountproperties toTopicRuntimeProperties, exposing the total number of SQL filters and correlation filters across all of a topic's subscriptions. These are populated byGetTopicRuntimePropertiesAsyncandGetTopicsRuntimePropertiesAsync.ServiceBusAdministrationClientOptions.ServiceVersion.V2024_05and made it the default service version. The topic filter counts above are served by the2024-05service API version, so the administration client now sendsapi-version=2024-05by default.GetMessageSessionsAsyncoverloads onServiceBusClientfor queues and subscriptions. The no-filter overload returns the IDs of sessions that have active messages or session state, and thesessionStateUpdatedAfteroverload returns session IDs whose session state was updated after the specified timestamp. Implements thecom.microsoft:get-message-sessionsAMQP management operation. (#58761)ServiceBusSessionReceiver, allowing a session to be cooperatively taken over by another receiver. SetServiceBusSessionReceiverOptions.EnableNonExclusiveSessionto accept a session non-exclusively, then read the token fromServiceBusSessionReceiver.SessionLockTokenand pass it asServiceBusSessionReceiverOptions.SessionLockToken = Guid.Parse(token)to take that session over.ServiceBusSessionReceiver.IsSessionExclusivereports the mode the session was established under. Dispositions for a non-exclusive session are routed over the management link so that settlement keeps working across a takeover, which lowers settlement throughput compared to an exclusive session. This applies toServiceBusSessionReceiveronly;ServiceBusSessionProcessorcontinues to lock sessions exclusively. Accepting a session withEnableNonExclusiveSessionset throwsNotSupportedExceptionwhen the endpoint declines it, either by refusing the request outright or by accepting it without assigning a lock token, which is how a caller detects whether the feature is available for a namespace. An endpoint that declines in some other way surfaces the exception its own error maps to. (#60060)Bugs Fixed
Fixed retry classification for web socket failures with nested causes. On modern .NET, a transient network failure during a web socket connection attempt surfaces as a
WebSocketExceptionthat wraps anHttpRequestException, which wraps the meaningfulIOExceptionorSocketException. The retry policy previously inspected only one level of nesting and treated these failures as terminal. The policy now unwraps nested wrapper exceptions to a bounded depth, so transient failures such as a connection reset use the configured retries. Terminal socket failures, such as host-not-found and host-unreachable, are not retried at any supported depth. A host-unreachable failure on an established connection is now terminal. Earlier versions retried it. (#61868)Fixed a bug where canceling
ServiceBusReceiver.CloseAsyncleft the receiver unable to close its own links. The receiver was marked as closed, and its set of locked messages disposed, before the cancellation was observed, so every later call toCloseAsyncreturned immediately without doing any work and the links stayed open until the owningServiceBusClientwas disposed. The receiver is now left open and closable when a close does not complete, so the operation can be retried. (#59309)Other Changes
ServiceBusAdministrationClientservice version is now2024-05(previously2021-05). Existing operations are unaffected in behavior; the change is required to surface the new topic filter count properties.Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions