Skip to content

feat: add support for containers/prune API#1002

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

feat: add support for containers/prune API#1002
bdraco merged 7 commits intoaio-libs:mainfrom
mdegat01:add-containers-prune

Conversation

@mdegat01
Copy link
Contributor

@mdegat01 mdegat01 commented Feb 4, 2026

What do these changes do?

Add support for the containers/prune API as detailed here: https://docs.docker.com/reference/api/engine/version/v1.53/#tag/Container/operation/ContainerPrune

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

No but as with #1001, #691 feels somewhat related as its listing prune APIs missing from the library

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."

@mdegat01 mdegat01 force-pushed the add-containers-prune branch 2 times, most recently from f68de98 to 82b3b07 Compare February 4, 2026 16:40
@codecov
Copy link

codecov bot commented Feb 4, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.31%. Comparing base (2351afe) to head (9a3b743).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1002      +/-   ##
==========================================
+ Coverage   73.22%   73.31%   +0.08%     
==========================================
  Files          25       25              
  Lines        1849     1855       +6     
  Branches      252      253       +1     
==========================================
+ Hits         1354     1360       +6     
  Misses        410      410              
  Partials       85       85              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@mdegat01 mdegat01 force-pushed the add-containers-prune branch from 4f7276d to a84d772 Compare February 13, 2026 16:13
@bdraco
Copy link
Member

bdraco commented Feb 13, 2026

ci failure looks like an upstream docker change we need to sort out first

Copy link
Member

@bdraco bdraco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @mdegat01

We will probably need to cleanup the changes in a future PR since it looks like we are still using RST and half migrated to markdown. I'll probably just fix them when I do the release since the content is there.

@bdraco bdraco enabled auto-merge (squash) February 13, 2026 17:35
@bdraco bdraco merged commit 771127a into aio-libs:main Feb 13, 2026
17 checks passed
@bdraco bdraco mentioned this pull request Feb 17, 2026
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

Comments