feat: add support for volumes/prune API#1003
Merged
bdraco merged 5 commits intoaio-libs:mainfrom Feb 13, 2026
Merged
Conversation
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.
What do these changes do?
Add support for the
volumes/pruneAPI, as detailed here: https://docs.docker.com/reference/api/engine/version/v1.53/#tag/Volume/operation/VolumePruneNote: I'm not currently in contributors but since I added myself as part of #1001 I figured I wouldn't add myself again here.
Are there changes in behavior for the user?
New method for a new API, no changes to existing functionality.
Related issue number
Requested as part of #691 here: #691 (comment)
Checklist
CONTRIBUTORS.txtchangesfolder<issue_id>.<type>for example (588.bug)issue_idchange it to the pr id after creating the pr.feature: Signifying a new feature..bugfix: Signifying a bug fix..doc: Signifying a documentation improvement..removal: Signifying a deprecation or removal of public API..misc: A ticket has been closed, but it is not of interest to users.