The audit event type `repository_download_operation` is currently saved to the database for all project downloads, both public projects and private projects. For
public projects, this audit event is not the most useful for auditing purposes because it can be triggered by non-authenticated users.
From GitLab 17.0, the `repository_download_operation` audit event type will only be triggered for private or internal projects. We will add a new audit event type
called `public_repository_download_operation` for public project downloads. This new audit even type will be streaming only.
### 'repository_download_operation' audit event type for public projects
<divclass="deprecation-notes">
- Announced in GitLab <spanclass="milestone">16.9</span>
- Removal in GitLab <spanclass="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change))
- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/383218).
</div>
The audit event type `repository_download_operation` is currently saved to the database for all project downloads, both public projects and private projects. For
public projects, this audit event is not the most useful for auditing purposes because it can be triggered by non-authenticated users.
From GitLab 17.0, the `repository_download_operation` audit event type will only be triggered for private or internal projects. We will add a new audit event type
called `public_repository_download_operation` for public project downloads. This new audit even type will be streaming only.