Skip to content

feat: add support for volumes/prune API#1003

Merged
bdraco merged 5 commits intoaio-libs:mainfrom
mdegat01:add-volumes-prune
Feb 13, 2026
Merged

feat: add support for volumes/prune API#1003
bdraco merged 5 commits intoaio-libs:mainfrom
mdegat01:add-volumes-prune

Conversation

@mdegat01
Copy link
Copy Markdown
Contributor

@mdegat01 mdegat01 commented Feb 4, 2026

What do these changes do?

Add support for the volumes/prune API, as detailed here: https://docs.docker.com/reference/api/engine/version/v1.53/#tag/Volume/operation/VolumePrune

Note: 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

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • If you provide code modification, please add yourself to CONTRIBUTORS.txt
    • The format is <Name> <Surname>.
    • Please keep alphabetical order, the file is sorted by names.
  • Add a new news fragment into the changes folder
    • name it <issue_id>.<type> for example (588.bug)
    • if you don't have an issue_id change it to the pr id after creating the pr
    • ensure type is one of the following:
      • .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.
    • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants