set artifacts visibility independent of the project or group visibility, i.e. Private, Internal, Public.
Description
It would be useful to be able to set artifacts visibility independent of the project or group visibility. Currently it is only possible to restrict access for public and internal projects [1]. However, there are cases were you would like to keep the project private or internal and expose the (last) artifact publicly, so that even non members can download the artifact. This is particular useful for ongoing documents and code (also everything) where you want/need to hide comments and other information only relevant for production while exposing a "cleaner" version of the artifact for review purposes.
Proposal
set artifacts visibility independent of the porject or group visibility, i.e. Private, Internal, Public.
Links / references
[1] https://gitlab.com/help/user/project/pipelines/settings#visibility-of-pipelines
Documentation blurb
Provides finer control of artifacts visibility. It can help to expose artifacts of private and internal repositories while keeping the repository files (source) accessible to members only. Conversely, access to artifacts of public or internal projects could be restricted to members only.
~"feature proposal"
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.