API to delete files from a package
You use the GitLab Package Registry to publish, install and share your dependencies. You may do this using a variety of package manager formats, such as Maven or npm. If you are doing this as part of your CI workflow, you may publish many packages to your registry. When you publish a dependency, it generates several files including the package archive.
The problem is that GitLab doesn't provide a way to delete the files from a package, only the package itself. These extra files can clutter the user interface or worse result in someone installing an incorrect or outdated dependency.
Moving forward, you can now use the Packages API to delete files related to a given package as well as the package itself.
Problem to solve
When packages are published to the GitLab Package Registry, there are several files uploaded to the registry. The file type and the number of files vary based on format, when you upload a package to the registry, files are generally uploaded.
These files are displayed in the application when you view a package's details. The problem is that we do not currently provide a way to delete the files only the packages themselves. As a given package/version can have many files, it can result in confusion when downloading files, result in user error, or just clutter the user interface.
As a Developer (or above), I'd like to be able to use the Packages API to delete specific files from a given package. This will be especially useful for removing branch-related packages uploaded to my registry during the build phase.
Following the current delete a package API, maybe implement something like:
Which would mean adding new attributes for file type file name.
By giving a way to delete package files, users can "corrupt" or "damage" a given package where an expected package file is missing. We will make it clear that this is the case in the Package documentation.
As a new feature, I'm most interested in adoption. So even a basic activity metric like the number of times it was used on GitLab.com would be helpful directionally.