I am wondering about package retention. Generally maven has the concept of snapshots, and nuget has the concept of prerelease packages. If I decide to have a CI like github actions that builds the project on push/merge of pull request, makes a nuget prerelease package and uploads it to github packages, are these prerelease packages ever deleted? the set of available packages can grow extremely large because each push would create one, and some similar solutions have a way to automatically clean up old prereleases.
At the moment there is no retention policy for package versions. It would be nice if there was a way to schedule cleanup of prerelease versions that haven’t been downloaded for a certain number of days.
Feel free to comment on this issue with any suggestions!
To be honest, isn’t it the case that deleting packages from public repositories is not available at all, currently?
Yes, this is indeed a problem.
This is a big need, especially if companies are looking to move various app build workflows to GitHub Actions.
I appreciate the option of having a way to do this via the
gpr tool but in my opinion this needs to be baked into GitHub.com so retention can be set per package and handled without custom work on the part of each GitHub customer.
Also, likewise for GitHub actions - specifying limits for action workflow run history / logs.
It’d also be nice to be able to setup defaults at the org level that can be overridden as needed at repo level.
I agree, this would be really useful to have… I only have 2Gb of storage so would like to let older versions go to make sure there is room for new ones.