Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove obsolete Maven artifacts from GitHub Packages #529

Merged
merged 2 commits into from
Nov 19, 2024

Conversation

MykytaPimonovTD
Copy link
Contributor

As noted in #522, many non-release artifacts in Spine's GitHub Packages are obsolete and no longer in use.

This changeset introduces a GitHub Actions workflow to automate the removal of these obsolete non-release artifacts from GitHub Packages.

An artifact is considered non-releasable if it includes the word “SNAPSHOT” in its version name. The workflow is scheduled to run daily at midnight. The removal task retains the five most recent non-release artifacts.

The artifact removal process follows these steps:

  1. Retrieves the names of packages created from this repository.

  2. For each package published from this repository, initiates a separate job to remove obsolete artifacts.

Additional details:

  1. Artifacts that are public and have been downloaded more than 5,000 times cannot be deleted. In such cases, contact GitHub Support for assistance.

  2. Up to 100 artifacts can be removed per run per package. If more than 100 obsolete artifacts exist, manually restart the workflow or wait for the next scheduled removal.

@MykytaPimonovTD MykytaPimonovTD self-assigned this Nov 19, 2024
@MykytaPimonovTD MykytaPimonovTD marked this pull request as ready for review November 19, 2024 09:19
@MykytaPimonovTD MykytaPimonovTD merged commit 27e60e3 into master Nov 19, 2024
2 checks passed
@MykytaPimonovTD MykytaPimonovTD deleted the remove-obsolete-artifacts branch November 19, 2024 10:42
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