gresb/Delete Release Candidates

Delete Release Candidates and related artefacts

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit May 5, 2026
License: MIT

Pinned Snippet

workflow.ymlSHA-pinned

uses: gresb/action-delete-release-candidates@62c3e6c83cef5fa062889c36613bd0594c7531c0 # v0.13.0

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
release-identifier	A string that will be used to identify the releases to be deleted (eg. "pr1234").	yes	—
keep-latest-count	The number of matches releases to keep, ordered from latest to oldest.	yes	0
ecr-name	The name of an ECR where to look for container images tagged with the releases we are deleting. The name is not the full URL, it is just the last bit of the URL.	no	—
s3-bucket	The name of a S3 bucket where to look for artefacts tagged with the releases we are deleting.	no	—
s3-object-key-prefix	The S3 object key prefix used to look for artefacts tagged with the releases we are deleting.	no	—
github-package-name	The name of the GitHub packages to delete.	no	—
github-package-type	The type of the GitHub packages to delete. See package_type under query parameters at https://docs.github.com/en/rest/packages/packages?apiVersion=2022-11-28#list-packages-for-an-organization--parameters	no	maven
github-token	The github token used to delete the releases and tags.	yes	—
aws-role-arn	The AWS IAM Role providing access to delete artefacts from either or both ECR and S3 Bucket.	no	—
aws-access-key-id	The AWS access key ID providing access to delete artefacts from either or both ECR and S3 Bucket.	no	—
aws-secret-access-key	The AWS secret access key providing access to delete artefacts from either or both ECR and S3 Bucket.	no	—
aws-region	The AWS region.	no	eu-central-1
dry-run	Whether to only print the artefacts that are matched for deletion instead of deleting them.	yes	true

Outputs

name	description
releases	The releases that were identified and deleted.