Deprecation notice for Dependency Proxy feature flag
This commit is contained in:
parent
b1246cf68a
commit
c45a9ca14a
|
@ -0,0 +1,11 @@
|
|||
- name: "Remove the `:dependency_proxy_for_private_groups` feature flag" # The name of the feature to be deprecated
|
||||
announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
|
||||
announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
|
||||
removal_milestone: "15.0" # The milestone when this feature is planned to be removed
|
||||
body: | # Do not modify this line, instead modify the lines below.
|
||||
We added a feature flag because [GitLab-#11582](https://gitlab.com/gitlab-org/gitlab/-/issues/11582) changed how public groups use the Dependency Proxy. Prior to this change, you could use the Dependency Proxy without authentication. The change requires authentication to use the Dependency Proxy.
|
||||
|
||||
In milestone 15.0, we will remove the feature flag entirely. Moving forward, you must authenticate when using the Dependency Proxy.
|
||||
stage: package
|
||||
tiers: Free
|
||||
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/276777
|
|
@ -115,6 +115,14 @@ When checking if a runner is `paused`, API users are advised to check the boolea
|
|||
|
||||
Announced: 2021-11-22
|
||||
|
||||
### Remove the `:dependency_proxy_for_private_groups` feature flag
|
||||
|
||||
We added a feature flag because [GitLab-#11582](https://gitlab.com/gitlab-org/gitlab/-/issues/11582) changed how public groups use the Dependency Proxy. Prior to this change, you could use the Dependency Proxy without authentication. The change requires authentication to use the Dependency Proxy.
|
||||
|
||||
In milestone 15.0, we will remove the feature flag entirely. Moving forward, you must authenticate when using the Dependency Proxy.
|
||||
|
||||
Announced: 2021-11-22
|
||||
|
||||
### `AuthenticationType` for `[runners.cache.s3]` must be explicitly assigned
|
||||
|
||||
In GitLab 15.0 and later, to access the AWS S3 cache, you must specify the `AuthenticationType` for [`[runners.cache.s3]`](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscaches3-section). The `AuthenticationType` must be `IAM` or `credentials`.
|
||||
|
|
Loading…
Reference in a new issue