Repository navigation
chore(deps)!: update asyncband to 0.8.0 - #8523
Merged
Merged
Conversation
PsiACE
approved these changes
Nov 16, 2026
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.
Which issue does this PR close?
Dependency maintenance; no linked issue.
Rationale for this change
Pick up the synchronization fixes and improvements in asyncband 0.8.0.
What changes are included in this PR?
Update the asyncband dependency in the core workspace, object_store integration, and C++, .NET, and Python bindings. Refresh the tracked core and Ruby lockfiles, and document the shared-semaphore migration.
Validated core Clippy across all targets and features, core and concurrent-limit unit tests, concurrent-limit doctests, object_store library tests, and Rust compilation of the C++, .NET, and Python bindings.
Are there any user-facing changes?
Applications supplying asyncband semaphores to
ConcurrentLimitLayermust use the new dependency version as described below.Breaking changes
Affected packages: core
Migration:
0.8with thesemaphorefeature when passingArc<asyncband::semaphore::Semaphore>toConcurrentLimitLayer::with_semaphoreorwith_http_semaphore.AI Usage Statement