diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-11-14 03:11:26 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-11-14 03:11:26 +0300 |
| commit | 2b8ac36bdd626226a93e6759b44bdcb5decc1559 (patch) | |
| tree | 32a0e6970564a00b2010a225d920f10f8e85a39c /doc/user/project/releases | |
| parent | 0851e2f024dfb983596d601f417ff485f33f39f8 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/releases')
| -rw-r--r-- | doc/user/project/releases/index.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/user/project/releases/index.md b/doc/user/project/releases/index.md index fd01dd451c2..75a25678125 100644 --- a/doc/user/project/releases/index.md +++ b/doc/user/project/releases/index.md @@ -462,6 +462,20 @@ In the API: This includes associated Git-tag-names, release description, author information of the releases. However, other repository-related information, such as [source code](release_fields.md#source-code), [release evidence](#release-evidence) are redacted. +### Publish releases without giving access to source code + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216485) in GitLab 15.6. + +Releases can be made accessible to non-project members while keeping repository-related information such as +[source code](release_fields.md#source-code) and [release evidence](#release-evidence) private. This is useful for +projects that use releases as a way to give access to new versions of software but do not want the source code to +be public. + +To make releases available publicly, set the following [project settings](../settings/index.md#project-feature-settings): + +- Repository is enabled and set to **Only Project Members** +- Releases is enabled and set to **Everyone With Access** + ### Create, update, and delete a release and its assets - Users with at least the Developer role |