Skip to content

feat(prune-pull-requests-images-tags)!: do not prune cache images by default#379

Merged
neilime merged 1 commit intomainfrom
feat/prune-pull-requests-images-tags-do-not-prune-cache-by-default
Mar 3, 2025
Merged

feat(prune-pull-requests-images-tags)!: do not prune cache images by default#379
neilime merged 1 commit intomainfrom
feat/prune-pull-requests-images-tags-do-not-prune-cache-by-default

Conversation

@neilime
Copy link
Copy Markdown
Member

@neilime neilime commented Mar 3, 2025

prune-pull-requests-images-tags: Cache images are no longer pruned by default, as it is a modification of an input it is a breaking change, but it should not impact project that are using docker-build-images to build images, then using prune-pull-requests-images-tags to clean them.

Tip

Since 0.19.0, docker-build-images is using gha backend cache, so no more cache image (ghcr.io/my-org/my-repo/my-image/cache) are created in the registry. It is reasonable to delete the existing one are they are useless.

…default

Signed-off-by: Emilien Escalle <emilien.escalle@escemi.com>
@neilime neilime merged commit 13fa4ed into main Mar 3, 2025
42 checks passed
@neilime neilime deleted the feat/prune-pull-requests-images-tags-do-not-prune-cache-by-default branch March 3, 2025 07:35
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.

1 participant