A GitHub Action to delete package versions from GitHub Packages with flexible retention policies.
Delete Package Versions is a GitHub Action that automates the deletion of package versions from GitHub Packages. It solves the problem of package repository clutter by allowing developers to implement retention policies, delete specific versions, and clean up pre-release or untagged packages directly within their CI/CD workflows.
Developers and DevOps engineers using GitHub Packages who need to automate package version cleanup to manage storage limits and maintain repository hygiene.
It provides a native, configurable solution within GitHub Actions for package lifecycle management, eliminating the need for custom scripts or manual deletion while supporting complex filtering and cross-repository operations.
Delete Package Versions is a GitHub Action that automates the cleanup of package versions stored in GitHub Packages. It helps developers manage storage costs and maintain organized repositories by removing outdated or unnecessary package versions through GitHub Actions workflows.
This action is designed to provide granular control over package version lifecycle management directly within CI/CD workflows, promoting automation and consistency in repository maintenance.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers flexible options like keeping the latest N versions or deleting oldest ones, with detailed examples in the README for scenarios such as deleting all except latest 2 versions.
Works with container, npm, NuGet, Maven, and RubyGems packages, as explicitly listed in the Key Features and required package-type input.
Can delete packages from repositories without direct access using tokens, detailed in scenarios for 'repo not having access to package' with owner and token inputs.
Allows ignoring specific versions using regex patterns, such as excluding major versions in semver with examples like '^(0|[1-9]\d*)\.0\.0$' in the ignore-versions input.
Only deletes up to 100 versions in a single workflow run, which is explicitly stated in the README and can be inefficient for large-scale cleanup operations.
The project is not taking contributions and focuses only on security updates and major breaking changes, as noted in the 'Note' section, potentially slowing bug fixes and feature enhancements.
Has specific input combinations that cannot be used together, such as num-old-versions-to-delete with delete-only-pre-release-versions, which might confuse users and lead to configuration errors.