Releases: snok/container-retention-policy
v1.5.0
This release adds the possibility of using wildcards in the image-names
attribute. This changes the behaviour of the action from a single-image retention tool, to potentially being used as a more general policy. See #39 for doc changes.
v1.4.2
v1.4.1
Fixes
- Pins regex downstream dependency to avoid dateparse failing (#28). See stackoverflow thread and dateparse issue for context.
v1.4.0
-
Makes the output for public images that cannot be deleted a little friendlier
-
Adds
deleted
,failed
, andneeds-github-assistance
action outputs, containing lists of images and versions.For those unfamiliar with how to interact with Github action outputs: if you specify and
id
of, e.g., "delete-images" to the action when run, you can access its outputs in subsequent steps, using${{ steps.delete-images.outputs.deleted }}
.The outputs can be used to, e.g., skip trying to delete the same images in subsequent runs. See this post for details.
Thanks @Siemienik for the idea, and help on the implementation.
v1.3.4
Limit action to running 50 requests concurrently. This fixes an issue where the HTTPX client would throw errors on exceeding 100 connections (#19)
v1.3.3
Add pydantic to refactor input validation (#17)
Should hopefully make input parsing a little bit more robust going forward.
v1.3.2
Fix bug in argument parsing (#16)
v1.3.1
Fix broken action argument parsing (#14)
v1.3.0
New features
- Added unix style wildcard support for the
skip-tags
input (#11) - Added
filter-tags
inputs, which can be used to filters container images. Supports wildcards (#12) - Added
filter-include-untagged
, which lets you opt-into including untagged images when usingfilter-tags
(#12)
Thanks @Emilgardis 👏
v1.2.1
Specifies '0'
as the default value for keep-at-least
. Right now it resolves as an empty string which is unhandled.