Publish and install generic packages using a deploy token
Release notes
GitLab Packages supports the publishing and downloading of 'generic packages' or raw binaries so that you can use the registry even if your format is not yet supported. For example, many of you are using the generic package format as a workaround for your Linux packages.
The problem is that you cannot use a deploy token when using generic packages. This is inconsistent with the rest of the Packages feature which supports publishing and installing packages with a deploy token. As a workaround you can your personal access token, but this is not ideal, especially at larger organizations.
Moving forward, you can use your deploy token when interacting with generic packages. We hope this new workflow will help you to be more efficient and secure.
Problem to solve
When publishing and installing generic packages, you can't use a project or group deploy token. This is problematic for organizations that prefer to avoid using a personal access token in their pipelines. It's also incongruent with the other package manager formats supported by GitLab Packages.
Proposal
Add support for authenticating with a project or group deploy token when publishing, installing, or viewing generic packages.