Is it possible to delete superfluous artifacts from a snapshot version?

[carlislefox]

Hi there,

Sorry to raise an issue for this but I can't figure it out using the readme alone. When you publish snapshots using maven you end up with an entire set of artifacts against a package with a different timestamp for every single build, this is resulting in me having a package version of say, 0.0.2-SNAPSHOT but it has a billion artifacts underneath it, a full set from each time the snapshot was built.

Is it possible to retain only the latest set of artifacts against a package version with this action? I only ever need the latest snapshot, I'm going to max my GitHub storage on one snapshot version at this rate :(

Thanks for your time, Fhox

[woj-tek]

Have you figured out how to do this?

[rvesse]

https://github.community/t/github-actions-to-purge-maven-repo-hosted-via-github-packages/165472/2

Looks like this isn't supported because they manage all the timestamped SNAPSHOT versions as a single version from GitHub Packages perspective

[woj-tek]

This is kinda terrible and... somewhat against maven principle? I'd say it's a bug on GitHub part...

[ArturJarosz]

Any news on that on? Or any way to remove accumulated SNAPSHOTs and to keep only newest one ?

[beradrian]

Two years after and there's not even a workaround for this? From what I understood the only workaround is to completely delete the version, which seems a little bit too much. It cannot apply for public packages and maybe you still want to keep x latest versions, not only the last. https://stackoverflow.com/questions/68521637/how-to-delete-old-snapshot-artifacts-from-github-packages