### Context The GitLab Container Registry has been undergoing significant changes. A year ago, we forked [Docker Distribution Registry](https://github.com/docker/distribution) so that we can add [zero downtime garbage collection](https://gitlab.com/groups/gitlab-org/-/epics/2313) and many other [features](https://gitlab.com/groups/gitlab-org/-/epics/2899). As we move closer to completing the above, it's worth pausing and thinking about the registry API and what improvements and changes will help folks using the registry to be more efficient. For example, https://gitlab.com/gitlab-org/gitlab/-/issues/217094 proposes adding pipeline and build meta data for each image tag. Or another popular issue, https://gitlab.com/gitlab-org/gitlab/-/issues/26983 which proposes removing branch-related images on merge. A plan for how the API will need to be expanded may help speed up future development and help Community members more easily contribute. ### Proposal Consider adding your thoughts, concerns, or questions to this issue about your ideas for the future state of the container registry API. Below you can see the most frequently requested, related issues.