diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-11-21 00:08:21 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-11-21 00:08:21 +0000 |
| commit | 2f76a4a875bc356b2c80f038e1ef4b835cbdfb4b (patch) | |
| tree | 0dfdac6575c447631adb5f113e268e4d0911b8b2 | |
| parent | 5d9d306884986036e730106098b103997caebfda (diff) | |
| download | gitlab-ce-2f76a4a875bc356b2c80f038e1ef4b835cbdfb4b.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
274 files changed, 458 insertions, 387 deletions
diff --git a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml index 778744c9363..b0746502713 100644 --- a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml +++ b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml @@ -1,4 +1,4 @@ -- name: "NFS for Git repository storage" # The name of the feature to be deprecated +- title: "NFS for Git repository storage" # The name of the feature to be deprecated announcement_milestone: "14.0" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-06-22" # The date of the milestone release when this feature was first announced as deprecated removal_milestone: "15.6" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-10-dependency-scanning-default-java-version.yml b/data/deprecations/14-10-dependency-scanning-default-java-version.yml index 1717c452891..c0ef84a562e 100644 --- a/data/deprecations/14-10-dependency-scanning-default-java-version.yml +++ b/data/deprecations/14-10-dependency-scanning-default-java-version.yml @@ -1,4 +1,4 @@ -- name: "Dependency Scanning default Java version changed to 17" +- title: "Dependency Scanning default Java version changed to 17" announcement_milestone: "14.10" announcement_date: "2022-04-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml b/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml index e5646f5123d..8a4dcd47e2c 100644 --- a/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml +++ b/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml @@ -1,4 +1,4 @@ -- name: "Toggle notes confidentiality on APIs" +- title: "Toggle notes confidentiality on APIs" announcement_milestone: "14.10" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-03-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: "16.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-10-old-search-migration-removal.yml b/data/deprecations/14-10-old-search-migration-removal.yml index a0074c53ffb..dd6161c2414 100644 --- a/data/deprecations/14-10-old-search-migration-removal.yml +++ b/data/deprecations/14-10-old-search-migration-removal.yml @@ -1,4 +1,4 @@ -- name: "Outdated indices of Advanced Search migrations" +- title: "Outdated indices of Advanced Search migrations" announcement_milestone: "14.10" announcement_date: "2021-04-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-2-deprecation-release-cli.yml b/data/deprecations/14-2-deprecation-release-cli.yml index fe53dea309a..f937728b944 100644 --- a/data/deprecations/14-2-deprecation-release-cli.yml +++ b/data/deprecations/14-2-deprecation-release-cli.yml @@ -1,4 +1,4 @@ -- name: "Release CLI distributed as a generic package" # The name of the feature to be deprecated +- title: "Release CLI distributed as a generic package" # The name of the feature to be deprecated announcement_milestone: "14.2" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-08-22" # The date of the milestone release when this feature was first announced as deprecated removal_milestone: "14.6" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-2-deprecation-task-runner.yml b/data/deprecations/14-2-deprecation-task-runner.yml index 1b72330c5bd..b69fb0969d5 100644 --- a/data/deprecations/14-2-deprecation-task-runner.yml +++ b/data/deprecations/14-2-deprecation-task-runner.yml @@ -1,4 +1,4 @@ -- name: "Rename Task Runner pod to Toolbox" # The name of the feature to be deprecated +- title: "Rename Task Runner pod to Toolbox" # The name of the feature to be deprecated announcement_milestone: "14.2" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-08-22" # The date of the milestone release when this feature was first announced as deprecated removal_milestone: "14.5" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml b/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml index 3644b681da0..829e1b39b0f 100644 --- a/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml +++ b/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml @@ -1,4 +1,4 @@ -- name: "Legacy database configuration" +- title: "Legacy database configuration" announcement_milestone: "14.3" announcement_date: "2021-09-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml b/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml index ba7c07eaf83..5f28497e982 100644 --- a/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml +++ b/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml @@ -1,4 +1,4 @@ -- name: "OmniAuth Kerberos gem" +- title: "OmniAuth Kerberos gem" announcement_milestone: "14.3" announcement_date: "2021-09-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-3-repository-push-audit-events.yml b/data/deprecations/14-3-repository-push-audit-events.yml index 033fa957320..bec376121da 100644 --- a/data/deprecations/14-3-repository-push-audit-events.yml +++ b/data/deprecations/14-3-repository-push-audit-events.yml @@ -1,4 +1,4 @@ -- name: "Audit events for repository push events" +- title: "Audit events for repository push events" announcement_milestone: "14.3" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-09-22" # https://gitlab.com/gitlab-org/gitlab/-/merge_requests/69024 removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/deprecations/14-3-serverless.yml b/data/deprecations/14-3-serverless.yml index 08a54046f4a..55a702c4d27 100644 --- a/data/deprecations/14-3-serverless.yml +++ b/data/deprecations/14-3-serverless.yml @@ -1,4 +1,4 @@ -- name: "GitLab Serverless" +- title: "GitLab Serverless" announcement_milestone: "14.3" announcement_date: "2021-09-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-5-certificate-based-integration-with-kubernetes-saas.yml b/data/deprecations/14-5-certificate-based-integration-with-kubernetes-saas.yml index 559189d759b..32e9f61db0c 100644 --- a/data/deprecations/14-5-certificate-based-integration-with-kubernetes-saas.yml +++ b/data/deprecations/14-5-certificate-based-integration-with-kubernetes-saas.yml @@ -1,4 +1,4 @@ -- name: "SaaS certificate-based integration with Kubernetes" +- title: "SaaS certificate-based integration with Kubernetes" announcement_milestone: "14.5" announcement_date: "2021-11-15" removal_milestone: "15.9" diff --git a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml index f76bd9f5424..44098f83c20 100644 --- a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml +++ b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml @@ -1,4 +1,4 @@ -- name: "Self-managed certificate-based integration with Kubernetes" +- title: "Self-managed certificate-based integration with Kubernetes" announcement_milestone: "14.5" announcement_date: "2021-11-15" removal_milestone: "17.0" diff --git a/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml b/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml index f6b47162a36..953af3634f7 100644 --- a/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml +++ b/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml @@ -1,4 +1,4 @@ -- name: "Changing an instance (shared) runner to a project (specific) runner" +- title: "Changing an instance (shared) runner to a project (specific) runner" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml index 17ce084ada6..447fb4e3ef5 100644 --- a/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml +++ b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml @@ -1,4 +1,4 @@ -- name: "`defaultMergeCommitMessageWithDescription` GraphQL API field" # The name of the feature to be deprecated +- title: "`defaultMergeCommitMessageWithDescription` GraphQL API field" # 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 diff --git a/data/deprecations/14-5-deprecate-opensuse-15-2.yml b/data/deprecations/14-5-deprecate-opensuse-15-2.yml index 877fcf7e3a6..abc30980c7f 100644 --- a/data/deprecations/14-5-deprecate-opensuse-15-2.yml +++ b/data/deprecations/14-5-deprecate-opensuse-15-2.yml @@ -1,4 +1,4 @@ -- name: "openSUSE Leap 15.2 packages" # The name of the feature to be deprecated +- title: "openSUSE Leap 15.2 packages" # 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: "14.8" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-deprecate-sles-12sp2.yml b/data/deprecations/14-5-deprecate-sles-12sp2.yml index adfbea4ce42..cc5bef6f203 100644 --- a/data/deprecations/14-5-deprecate-sles-12sp2.yml +++ b/data/deprecations/14-5-deprecate-sles-12sp2.yml @@ -1,4 +1,4 @@ -- name: "Support for SLES 12 SP2" # The name of the feature to be deprecated +- title: "Support for SLES 12 SP2" # 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" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-deprecation-versions-packagetype.yml b/data/deprecations/14-5-deprecation-versions-packagetype.yml index da6e705b94f..110bb9f218f 100644 --- a/data/deprecations/14-5-deprecation-versions-packagetype.yml +++ b/data/deprecations/14-5-deprecation-versions-packagetype.yml @@ -1,4 +1,4 @@ -- name: "`Versions` on base `PackageType`" +- title: "`Versions` on base `PackageType`" 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 diff --git a/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml b/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml index 0ba7b828f8d..10ed8ff8ad6 100644 --- a/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml +++ b/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml @@ -1,4 +1,4 @@ -- name: "Value Stream Analytics filtering calculation change" # The name of the feature to be deprecated +- title: "Value Stream Analytics filtering calculation change" # 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 diff --git a/data/deprecations/14-5-disable_strict_host_key_checking.yml b/data/deprecations/14-5-disable_strict_host_key_checking.yml index b2091578ff4..c5677dd8c3c 100644 --- a/data/deprecations/14-5-disable_strict_host_key_checking.yml +++ b/data/deprecations/14-5-disable_strict_host_key_checking.yml @@ -1,4 +1,4 @@ -- name: "Known host required for GitLab Runner SSH executor" +- title: "Known host required for GitLab Runner SSH executor" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-geo-deprecate-promote-db.yml b/data/deprecations/14-5-geo-deprecate-promote-db.yml index 0dbd785c1a0..4aedc7a8876 100644 --- a/data/deprecations/14-5-geo-deprecate-promote-db.yml +++ b/data/deprecations/14-5-geo-deprecate-promote-db.yml @@ -1,4 +1,4 @@ -- name: "`promote-db` command from `gitlab-ctl`" # The name of the feature to be deprecated +- title: "`promote-db` command from `gitlab-ctl`" # 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 diff --git a/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml index 69034bcd33d..048a78aedc7 100644 --- a/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml +++ b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml @@ -1,4 +1,4 @@ -- name: "`promote-to-primary-node` command from `gitlab-ctl`" # The name of the feature to be deprecated +- title: "`promote-to-primary-node` command from `gitlab-ctl`" # 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 diff --git a/data/deprecations/14-5-package-container-registry-api-group-update.yml b/data/deprecations/14-5-package-container-registry-api-group-update.yml index 67e3557cae3..40174c02e50 100644 --- a/data/deprecations/14-5-package-container-registry-api-group-update.yml +++ b/data/deprecations/14-5-package-container-registry-api-group-update.yml @@ -1,4 +1,4 @@ -- name: "Update to the Container Registry group-level API" +- title: "Update to the Container Registry group-level API" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml b/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml index 2229637f527..0d9fe9c9539 100644 --- a/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml +++ b/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml @@ -1,4 +1,4 @@ -- name: "`dependency_proxy_for_private_groups` feature flag" # The name of the feature to be deprecated +- title: "`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 diff --git a/data/deprecations/14-5-remove-package-pipelines-api.yml b/data/deprecations/14-5-remove-package-pipelines-api.yml index 91b2971297f..0cf2201d6e3 100644 --- a/data/deprecations/14-5-remove-package-pipelines-api.yml +++ b/data/deprecations/14-5-remove-package-pipelines-api.yml @@ -1,4 +1,4 @@ -- name: "Package pipelines in API payload is paginated" # The name of the feature to be deprecated +- title: "Package pipelines in API payload is paginated" # 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: "16.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-remove-pipelines-from-version-field.yml b/data/deprecations/14-5-remove-pipelines-from-version-field.yml index 98174daa26c..0470bba35cc 100644 --- a/data/deprecations/14-5-remove-pipelines-from-version-field.yml +++ b/data/deprecations/14-5-remove-pipelines-from-version-field.yml @@ -1,4 +1,4 @@ -- name: "`pipelines` field from the `version` field" # The name of the feature to be deprecated +- title: "`pipelines` field from the `version` field" # 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 diff --git a/data/deprecations/14-5-runner-api-status-does-contain-paused.yml b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml index 41124638509..75a0a7de666 100644 --- a/data/deprecations/14-5-runner-api-status-does-contain-paused.yml +++ b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml @@ -1,4 +1,4 @@ -- name: "GraphQL API Runner status will not return `paused`" +- title: "GraphQL API Runner status will not return `paused`" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" removal_milestone: "16.0" # the milestone when this feature is planned to be removed diff --git a/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml b/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml index b80fd45239e..614a1bc73d5 100644 --- a/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml +++ b/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml @@ -1,4 +1,4 @@ -- name: "Enforced validation of security report schemas" # The name of the feature to be deprecated +- title: "Enforced validation of security report schemas" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/14-6-container-scanning-schemas-below-14.yml b/data/deprecations/14-6-container-scanning-schemas-below-14.yml index 9427c9f0e88..244c5662b25 100644 --- a/data/deprecations/14-6-container-scanning-schemas-below-14.yml +++ b/data/deprecations/14-6-container-scanning-schemas-below-14.yml @@ -1,4 +1,4 @@ -- name: "Container scanning schemas below 14.0.0" # The name of the feature to be deprecated +- title: "Container scanning schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml b/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml index 78d076294ed..dcb643d5787 100644 --- a/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml +++ b/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml @@ -1,4 +1,4 @@ -- name: "Coverage guided fuzzing schemas below 14.0.0" # The name of the feature to be deprecated +- title: "Coverage guided fuzzing schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/14-6-dast-schemas-below-14.yml b/data/deprecations/14-6-dast-schemas-below-14.yml index 305cf9469f9..8ff3d899951 100644 --- a/data/deprecations/14-6-dast-schemas-below-14.yml +++ b/data/deprecations/14-6-dast-schemas-below-14.yml @@ -1,4 +1,4 @@ -- name: "DAST schemas below 14.0.0" # The name of the feature to be deprecated +- title: "DAST schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml b/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml index f04130bc68f..5255779f5a8 100644 --- a/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml +++ b/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml @@ -1,4 +1,4 @@ -- name: "Dependency scanning schemas below 14.0.0" # The name of the feature to be deprecated +- title: "Dependency scanning schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/14-6-deprecate-types.yml b/data/deprecations/14-6-deprecate-types.yml index 7f6c1a4cfa5..c2afcc8226d 100644 --- a/data/deprecations/14-6-deprecate-types.yml +++ b/data/deprecations/14-6-deprecate-types.yml @@ -1,4 +1,4 @@ -- name: "`type` and `types` keyword in CI/CD configuration" # The name of the feature to be deprecated +- title: "`type` and `types` keyword in CI/CD configuration" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-12-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 diff --git a/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml index 344d1a04a4b..03bfd5e1a7b 100644 --- a/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml +++ b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml @@ -1,4 +1,4 @@ -- name: "Legacy approval status names from License Compliance API" # The name of the feature to be deprecated +- title: "Legacy approval status names from License Compliance API" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-12-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 diff --git a/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml index 72039930348..5321c23e797 100644 --- a/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml +++ b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml @@ -1,4 +1,4 @@ -- name: "bundler-audit Dependency Scanning tool" # The name of the feature to be deprecated +- title: "bundler-audit Dependency Scanning tool" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-12-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 diff --git a/data/deprecations/14-6-job_char_limit.yml b/data/deprecations/14-6-job_char_limit.yml index b7dff12da5f..a1422f57506 100644 --- a/data/deprecations/14-6-job_char_limit.yml +++ b/data/deprecations/14-6-job_char_limit.yml @@ -1,4 +1,4 @@ -- name: "CI/CD job name length limit" # The name of the feature to be deprecated +- title: "CI/CD job name length limit" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-12-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 diff --git a/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml b/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml index bdf7a64700b..639c48f7302 100644 --- a/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml +++ b/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml @@ -1,4 +1,4 @@ -- name: "apiFuzzingCiConfigurationCreate GraphQL mutation" +- title: "apiFuzzingCiConfigurationCreate GraphQL mutation" announcement_milestone: "14.6" announcement_date: "2021-12-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-6-sast-schemas-below-14.yml b/data/deprecations/14-6-sast-schemas-below-14.yml index 635eaa3624b..9afab73e316 100644 --- a/data/deprecations/14-6-sast-schemas-below-14.yml +++ b/data/deprecations/14-6-sast-schemas-below-14.yml @@ -1,4 +1,4 @@ -- name: "SAST schemas below 14.0.0" # The name of the feature to be deprecated +- title: "SAST schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/14-6-secret-detection-schemas-below-14.yml b/data/deprecations/14-6-secret-detection-schemas-below-14.yml index 16af233df44..53c9cf89795 100644 --- a/data/deprecations/14-6-secret-detection-schemas-below-14.yml +++ b/data/deprecations/14-6-secret-detection-schemas-below-14.yml @@ -1,4 +1,4 @@ -- name: "Secret detection schemas below 14.0.0" # The name of the feature to be deprecated +- title: "Secret detection schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/14-7-deprecate-artifacts-keyword.yml b/data/deprecations/14-7-deprecate-artifacts-keyword.yml index 26fd6b485df..e4c82ebcc24 100644 --- a/data/deprecations/14-7-deprecate-artifacts-keyword.yml +++ b/data/deprecations/14-7-deprecate-artifacts-keyword.yml @@ -1,4 +1,4 @@ -- name: "`artifacts:reports:cobertura` keyword" +- title: "`artifacts:reports:cobertura` keyword" announcement_milestone: "14.7" announcement_date: "2022-01-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml b/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml index 9d0e2aa91dc..080853e6f1e 100644 --- a/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml +++ b/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml @@ -1,4 +1,4 @@ -- name: "Godep support in License Compliance" # The name of the feature to be deprecated +- title: "Godep support in License Compliance" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/14-7-deprecate-merged_by-api-field.yml b/data/deprecations/14-7-deprecate-merged_by-api-field.yml index 561f3d5360e..623a544052a 100644 --- a/data/deprecations/14-7-deprecate-merged_by-api-field.yml +++ b/data/deprecations/14-7-deprecate-merged_by-api-field.yml @@ -10,7 +10,7 @@ # # Please delete this line and above before submitting your merge request. -- name: "merged_by API field" # The name of the feature to be deprecated +- title: "merged_by API field" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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: "16.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-7-deprecate-static-site-editor.yml b/data/deprecations/14-7-deprecate-static-site-editor.yml index 7d1d324c0ca..f44f4f3f256 100644 --- a/data/deprecations/14-7-deprecate-static-site-editor.yml +++ b/data/deprecations/14-7-deprecate-static-site-editor.yml @@ -1,4 +1,4 @@ -- name: "Static Site Editor" # The name of the feature to be deprecated +- title: "Static Site Editor" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/14-7-pseudonymizer.yml b/data/deprecations/14-7-pseudonymizer.yml index f278cd506e2..43987332210 100644 --- a/data/deprecations/14-7-pseudonymizer.yml +++ b/data/deprecations/14-7-pseudonymizer.yml @@ -1,4 +1,4 @@ -- name: "Pseudonymizer" # The name of the feature to be deprecated +- title: "Pseudonymizer" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml b/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml index 1faec65e9ef..324339a45ea 100644 --- a/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml +++ b/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml @@ -1,4 +1,4 @@ -- name: "Sidekiq metrics and health checks configuration" +- title: "Sidekiq metrics and health checks configuration" announcement_milestone: "14.7" announcement_date: "2021-01-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-Elasticsearch-6-8.yml b/data/deprecations/14-8-Elasticsearch-6-8.yml index e52e237ffbc..d9b7f607f27 100644 --- a/data/deprecations/14-8-Elasticsearch-6-8.yml +++ b/data/deprecations/14-8-Elasticsearch-6-8.yml @@ -1,4 +1,4 @@ -- name: "Elasticsearch 6.8" +- title: "Elasticsearch 6.8" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-ci-build-variables.yml b/data/deprecations/14-8-ci-build-variables.yml index dba841841f2..de531becdab 100644 --- a/data/deprecations/14-8-ci-build-variables.yml +++ b/data/deprecations/14-8-ci-build-variables.yml @@ -1,4 +1,4 @@ -- name: "`CI_BUILD_*` predefined variables" +- title: "`CI_BUILD_*` predefined variables" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "16.0" diff --git a/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml b/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml index aabd330d567..1b262c98d40 100644 --- a/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml +++ b/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml @@ -1,4 +1,4 @@ -- name: "Required pipeline configurations in Premium tier" +- title: "Required pipeline configurations in Premium tier" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-compliance-status-check-api-field.yml b/data/deprecations/14-8-compliance-status-check-api-field.yml index ba8c84343bd..6493905a6d5 100644 --- a/data/deprecations/14-8-compliance-status-check-api-field.yml +++ b/data/deprecations/14-8-compliance-status-check-api-field.yml @@ -1,4 +1,4 @@ -- name: "External status check API breaking changes" +- title: "External status check API breaking changes" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml b/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml index 36104ad15d8..f2fd11ceb28 100644 --- a/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml +++ b/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml @@ -1,4 +1,4 @@ -- name: "`projectFingerprint` in `PipelineSecurityReportFinding` GraphQL" # The name of the feature to be deprecated +- title: "`projectFingerprint` in `PipelineSecurityReportFinding` GraphQL" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml b/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml index 3713ae532b3..070262707a9 100644 --- a/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml +++ b/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml @@ -1,4 +1,4 @@ -- name: "Retire-JS Dependency Scanning tool" # The name of the feature to be deprecated +- title: "Retire-JS Dependency Scanning tool" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/14-8-enforce-pat-expiration.yml b/data/deprecations/14-8-enforce-pat-expiration.yml index bc8e35a4e2c..6f165bbdb19 100644 --- a/data/deprecations/14-8-enforce-pat-expiration.yml +++ b/data/deprecations/14-8-enforce-pat-expiration.yml @@ -1,4 +1,4 @@ -- name: "Optional enforcement of PAT expiration" # The name of the feature to be deprecated +- title: "Optional enforcement of PAT expiration" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/14-8-enforce-ssh-expiration.yml b/data/deprecations/14-8-enforce-ssh-expiration.yml index 5887e749d2c..d772adf1b4c 100644 --- a/data/deprecations/14-8-enforce-ssh-expiration.yml +++ b/data/deprecations/14-8-enforce-ssh-expiration.yml @@ -1,4 +1,4 @@ -- name: "Optional enforcement of SSH expiration" # The name of the feature to be deprecated +- title: "Optional enforcement of SSH expiration" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml b/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml index d38e579e3e6..0390632968a 100644 --- a/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml +++ b/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml @@ -1,4 +1,4 @@ -- name: "Deprecate custom Geo:db:* Rake tasks" +- title: "Deprecate custom Geo:db:* Rake tasks" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml b/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml index c28dc849f72..c4a4117f0cd 100644 --- a/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml +++ b/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml @@ -1,4 +1,4 @@ -- name: "Deprecate Geo Admin UI Routes" +- title: "Deprecate Geo Admin UI Routes" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml b/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml index 861bed1e976..0273559a268 100644 --- a/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml +++ b/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml @@ -1,4 +1,4 @@ -- name: "Deprecate legacy Gitaly configuration methods" # The name of the feature to be deprecated +- title: "Deprecate legacy Gitaly configuration methods" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/14-8-gitaly-remove-per-repository-election.yml b/data/deprecations/14-8-gitaly-remove-per-repository-election.yml index 7edaff9821f..88412780048 100644 --- a/data/deprecations/14-8-gitaly-remove-per-repository-election.yml +++ b/data/deprecations/14-8-gitaly-remove-per-repository-election.yml @@ -1,4 +1,4 @@ -- name: "Configurable Gitaly `per_repository` election strategy" # The name of the feature to be deprecated +- title: "Configurable Gitaly `per_repository` election strategy" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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: "14.9" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-8-graphql-ids.yml b/data/deprecations/14-8-graphql-ids.yml index 899ff323792..344e7a8cef5 100644 --- a/data/deprecations/14-8-graphql-ids.yml +++ b/data/deprecations/14-8-graphql-ids.yml @@ -1,4 +1,4 @@ -- name: "GraphQL ID and GlobalID compatibility" +- title: "GraphQL ID and GlobalID compatibility" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-grpc-proxy.yml b/data/deprecations/14-8-grpc-proxy.yml index 9d161dbc8f9..9f7a044d154 100644 --- a/data/deprecations/14-8-grpc-proxy.yml +++ b/data/deprecations/14-8-grpc-proxy.yml @@ -1,4 +1,4 @@ -- name: "Support for gRPC-aware proxy deployed between Gitaly and rest of GitLab" +- title: "Support for gRPC-aware proxy deployed between Gitaly and rest of GitLab" announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/14-8-iteration-started-field.yml b/data/deprecations/14-8-iteration-started-field.yml index e323b93752b..a4401632682 100644 --- a/data/deprecations/14-8-iteration-started-field.yml +++ b/data/deprecations/14-8-iteration-started-field.yml @@ -1,4 +1,4 @@ -- name: "`started` iterations API field" # The name of the feature to be deprecated +- title: "`started` iterations API field" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/14-8-protect-cns-chs.yml b/data/deprecations/14-8-protect-cns-chs.yml index 6fb67e98b2c..098b571f9fb 100644 --- a/data/deprecations/14-8-protect-cns-chs.yml +++ b/data/deprecations/14-8-protect-cns-chs.yml @@ -1,4 +1,4 @@ -- name: "Container Network and Host Security" +- title: "Container Network and Host Security" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-protect-vulnerability-check.yml b/data/deprecations/14-8-protect-vulnerability-check.yml index ddb296886b2..737756ae8ac 100644 --- a/data/deprecations/14-8-protect-vulnerability-check.yml +++ b/data/deprecations/14-8-protect-vulnerability-check.yml @@ -1,4 +1,4 @@ -- name: "Vulnerability Check" +- title: "Vulnerability Check" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml b/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml index 4029443cc76..daffe46ee47 100644 --- a/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml +++ b/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml @@ -1,4 +1,4 @@ -- name: "Deprecate feature flag PUSH_RULES_SUPERSEDE_CODE_OWNERS" # The name of the feature to be deprecated +- title: "Deprecate feature flag PUSH_RULES_SUPERSEDE_CODE_OWNERS" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/14-8-request-profiling.yml b/data/deprecations/14-8-request-profiling.yml index e6c20abf2b1..eb7ab356d27 100644 --- a/data/deprecations/14-8-request-profiling.yml +++ b/data/deprecations/14-8-request-profiling.yml @@ -1,4 +1,4 @@ -- name: "Request profiling" +- title: "Request profiling" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml b/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml index 223c1439191..358192888ad 100644 --- a/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml +++ b/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml @@ -1,4 +1,4 @@ -- name: "REST and GraphQL API Runner usage of `active` replaced by `paused`" +- title: "REST and GraphQL API Runner usage of `active` replaced by `paused`" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "16.0" diff --git a/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml b/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml index 376a27c8863..d652346a8fa 100644 --- a/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml +++ b/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml @@ -1,4 +1,4 @@ -- name: "GraphQL API Runner will not accept `status` filter values of `active` or `paused`" +- title: "GraphQL API Runner will not accept `status` filter values of `active` or `paused`" announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-22" removal_milestone: "16.0" diff --git a/data/deprecations/14-8-sast-analyzer-removals.yml b/data/deprecations/14-8-sast-analyzer-removals.yml index 4c4675be808..0ad3920669a 100644 --- a/data/deprecations/14-8-sast-analyzer-removals.yml +++ b/data/deprecations/14-8-sast-analyzer-removals.yml @@ -1,4 +1,4 @@ -- name: "SAST analyzer consolidation and CI/CD template changes" +- title: "SAST analyzer consolidation and CI/CD template changes" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.4" diff --git a/data/deprecations/14-8-sast-dotnet-21.yml b/data/deprecations/14-8-sast-dotnet-21.yml index ab1b3c16b23..1a09329244d 100644 --- a/data/deprecations/14-8-sast-dotnet-21.yml +++ b/data/deprecations/14-8-sast-dotnet-21.yml @@ -1,4 +1,4 @@ -- name: "SAST support for .NET 2.1" +- title: "SAST support for .NET 2.1" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-sast-secret-analyzer-image.yml b/data/deprecations/14-8-sast-secret-analyzer-image.yml index cc7e559722d..e774941ace4 100644 --- a/data/deprecations/14-8-sast-secret-analyzer-image.yml +++ b/data/deprecations/14-8-sast-secret-analyzer-image.yml @@ -1,4 +1,4 @@ -- name: "Secure and Protect analyzer images published in new location" +- title: "Secure and Protect analyzer images published in new location" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-sast-spotbugs-java-8.yml b/data/deprecations/14-8-sast-spotbugs-java-8.yml index 3e3672eeb63..58d1e205aad 100644 --- a/data/deprecations/14-8-sast-spotbugs-java-8.yml +++ b/data/deprecations/14-8-sast-spotbugs-java-8.yml @@ -1,4 +1,4 @@ -- name: "Out-of-the-box SAST support for Java 8" +- title: "Out-of-the-box SAST support for Java 8" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-secret-detection-configurations.yml b/data/deprecations/14-8-secret-detection-configurations.yml index f9103c1cea3..8078d7c6fa0 100644 --- a/data/deprecations/14-8-secret-detection-configurations.yml +++ b/data/deprecations/14-8-secret-detection-configurations.yml @@ -1,4 +1,4 @@ -- name: "Secret Detection configuration variables deprecated" +- title: "Secret Detection configuration variables deprecated" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-8-secure-and-protect-analyzer-bump.yml b/data/deprecations/14-8-secure-and-protect-analyzer-bump.yml index dafa8b4cdc7..e1616cd1f6e 100644 --- a/data/deprecations/14-8-secure-and-protect-analyzer-bump.yml +++ b/data/deprecations/14-8-secure-and-protect-analyzer-bump.yml @@ -1,4 +1,4 @@ -- name: "Secure and Protect analyzer major version update" # The name of the feature to be deprecated +- title: "Secure and Protect analyzer major version update" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/14-8-secure-ca-python-deprecation.yml b/data/deprecations/14-8-secure-ca-python-deprecation.yml index 21b3b01a590..fab7455fe1c 100644 --- a/data/deprecations/14-8-secure-ca-python-deprecation.yml +++ b/data/deprecations/14-8-secure-ca-python-deprecation.yml @@ -1,4 +1,4 @@ -- name: "Dependency Scanning Python 3.9 and 3.6 image deprecation" # The name of the feature to be deprecated +- title: "Dependency Scanning Python 3.9 and 3.6 image deprecation" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-02-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 diff --git a/data/deprecations/14-9-background-upload.yml b/data/deprecations/14-9-background-upload.yml index ae9b1bd9a4a..e336cb7d39c 100644 --- a/data/deprecations/14-9-background-upload.yml +++ b/data/deprecations/14-9-background-upload.yml @@ -1,4 +1,4 @@ -- name: "Background upload for object storage" +- title: "Background upload for object storage" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-9-deprecate-composer-download-permissions.yml b/data/deprecations/14-9-deprecate-composer-download-permissions.yml index e44f1c55167..47e1502c466 100644 --- a/data/deprecations/14-9-deprecate-composer-download-permissions.yml +++ b/data/deprecations/14-9-deprecate-composer-download-permissions.yml @@ -1,4 +1,4 @@ -- name: "Permissions change for downloading Composer dependencies" +- title: "Permissions change for downloading Composer dependencies" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "14.10" diff --git a/data/deprecations/14-9-deprecate-debian-9.yml b/data/deprecations/14-9-deprecate-debian-9.yml index 3dce4892ab7..7057ceb4176 100644 --- a/data/deprecations/14-9-deprecate-debian-9.yml +++ b/data/deprecations/14-9-deprecate-debian-9.yml @@ -1,4 +1,4 @@ -- name: "Deprecate support for Debian 9" +- title: "Deprecate support for Debian 9" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "15.1" diff --git a/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml b/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml index 366f0e83470..9e6da8c8776 100644 --- a/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml +++ b/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml @@ -1,4 +1,4 @@ -- name: "GraphQL permissions change for Package settings" +- title: "GraphQL permissions change for Package settings" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-9-deprecate-testcoveragesetting.yml b/data/deprecations/14-9-deprecate-testcoveragesetting.yml index e6dfb22562b..9532a34b568 100644 --- a/data/deprecations/14-9-deprecate-testcoveragesetting.yml +++ b/data/deprecations/14-9-deprecate-testcoveragesetting.yml @@ -1,4 +1,4 @@ -- name: "Test coverage project CI/CD setting" # The name of the feature to be deprecated +- title: "Test coverage project CI/CD setting" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/14-9-deprecation-htpassword-authentication-container-registry.yml b/data/deprecations/14-9-deprecation-htpassword-authentication-container-registry.yml index 5d940b5e14d..0090a960417 100644 --- a/data/deprecations/14-9-deprecation-htpassword-authentication-container-registry.yml +++ b/data/deprecations/14-9-deprecation-htpassword-authentication-container-registry.yml @@ -1,4 +1,4 @@ -- name: "htpasswd Authentication for the Container Registry" +- title: "htpasswd Authentication for the Container Registry" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-9-global-search-deprecate-user-email-lookup-limit.yml b/data/deprecations/14-9-global-search-deprecate-user-email-lookup-limit.yml index 2b986a11d47..f69ac6e9a82 100644 --- a/data/deprecations/14-9-global-search-deprecate-user-email-lookup-limit.yml +++ b/data/deprecations/14-9-global-search-deprecate-user-email-lookup-limit.yml @@ -1,4 +1,4 @@ -- name: "user_email_lookup_limit API field" +- title: "user_email_lookup_limit API field" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-9-pages-daemon.yml b/data/deprecations/14-9-pages-daemon.yml index a8fb5924ac6..827daf18c21 100644 --- a/data/deprecations/14-9-pages-daemon.yml +++ b/data/deprecations/14-9-pages-daemon.yml @@ -1,4 +1,4 @@ -- name: "GitLab Pages running as daemon" # The name of the feature to be deprecated +- title: "GitLab Pages running as daemon" # The name of the feature to be deprecated announcement_milestone: "14.9" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-03-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 diff --git a/data/deprecations/14-9-system_monitoring.yml b/data/deprecations/14-9-system_monitoring.yml index c4b3343bee6..10d0a6db422 100644 --- a/data/deprecations/14-9-system_monitoring.yml +++ b/data/deprecations/14-9-system_monitoring.yml @@ -1,4 +1,4 @@ -- name: "GitLab self-monitoring project" # The name of the feature to be deprecated +- title: "GitLab self-monitoring project" # The name of the feature to be deprecated announcement_milestone: "14.9" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-03-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: "16.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-0-ci-cd-settings-update-mutation-renamed.yml b/data/deprecations/15-0-ci-cd-settings-update-mutation-renamed.yml index 7f426190963..4f8fc40fd73 100644 --- a/data/deprecations/15-0-ci-cd-settings-update-mutation-renamed.yml +++ b/data/deprecations/15-0-ci-cd-settings-update-mutation-renamed.yml @@ -1,4 +1,4 @@ -- name: "CiCdSettingsUpdate mutation renamed to ProjectCiCdSettingsUpdate" +- title: "CiCdSettingsUpdate mutation renamed to ProjectCiCdSettingsUpdate" announcement_milestone: "15.0" announcement_date: "2022-05-22" removal_milestone: "16.0" diff --git a/data/deprecations/15-0-deprecate-monitor-logging.yml b/data/deprecations/15-0-deprecate-monitor-logging.yml index 8dbae6f5c4c..62f889e666f 100644 --- a/data/deprecations/15-0-deprecate-monitor-logging.yml +++ b/data/deprecations/15-0-deprecate-monitor-logging.yml @@ -1,4 +1,4 @@ -- name: "Logging in GitLab" # The name of the feature to be deprecated +- title: "Logging in GitLab" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/15-0-deprecate-monitor-metrics.yml b/data/deprecations/15-0-deprecate-monitor-metrics.yml index 9ad78d9c01d..652845f0090 100644 --- a/data/deprecations/15-0-deprecate-monitor-metrics.yml +++ b/data/deprecations/15-0-deprecate-monitor-metrics.yml @@ -1,4 +1,4 @@ -- name: "Monitor performance metrics through Prometheus" # The name of the feature to be deprecated +- title: "Monitor performance metrics through Prometheus" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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: "16.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-0-deprecate-monitor-tracing.yml b/data/deprecations/15-0-deprecate-monitor-tracing.yml index 3c1eef177ff..3989ea2ed68 100644 --- a/data/deprecations/15-0-deprecate-monitor-tracing.yml +++ b/data/deprecations/15-0-deprecate-monitor-tracing.yml @@ -1,4 +1,4 @@ -- name: "Tracing in GitLab" # The name of the feature to be deprecated +- title: "Tracing in GitLab" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-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 diff --git a/data/deprecations/15-0-deprecate-postgresql-12.yml b/data/deprecations/15-0-deprecate-postgresql-12.yml index bebfba64405..1cf463d9411 100644 --- a/data/deprecations/15-0-deprecate-postgresql-12.yml +++ b/data/deprecations/15-0-deprecate-postgresql-12.yml @@ -1,4 +1,4 @@ -- name: "PostgreSQL 12 deprecated" +- title: "PostgreSQL 12 deprecated" announcement_milestone: "15.0" announcement_date: "2022-05-22" removal_milestone: "16.0" diff --git a/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml b/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml index 113ccdc66ea..5d2527094f9 100644 --- a/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml +++ b/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml @@ -1,4 +1,4 @@ -- name: "Querying Usage Trends via the `instanceStatisticsMeasurements` GraphQL node" +- title: "Querying Usage Trends via the `instanceStatisticsMeasurements` GraphQL node" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/deprecations/15-0-oauth-noexpiry.yml b/data/deprecations/15-0-oauth-noexpiry.yml index 9f2521998aa..88ccb7702b8 100644 --- a/data/deprecations/15-0-oauth-noexpiry.yml +++ b/data/deprecations/15-0-oauth-noexpiry.yml @@ -1,4 +1,4 @@ -- name: "OAuth tokens without expiration" # The name of the feature to be deprecated +- title: "OAuth tokens without expiration" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/deprecations/15-0-oauth.yml b/data/deprecations/15-0-oauth.yml index 7e1c3ff51cd..b7af6b51afc 100644 --- a/data/deprecations/15-0-oauth.yml +++ b/data/deprecations/15-0-oauth.yml @@ -1,4 +1,4 @@ -- name: "OAuth implicit grant" # The name of the feature to be deprecated +- title: "OAuth implicit grant" # The name of the feature to be deprecated announcement_milestone: "14.0" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-06-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 diff --git a/data/deprecations/15-0-runner-status-legacy-mode.yml b/data/deprecations/15-0-runner-status-legacy-mode.yml index ee7ac1af820..dfdbf6e5f58 100644 --- a/data/deprecations/15-0-runner-status-legacy-mode.yml +++ b/data/deprecations/15-0-runner-status-legacy-mode.yml @@ -1,4 +1,4 @@ -- name: "GraphQL API legacyMode argument for Runner status" # The name of the feature to be deprecated +- title: "GraphQL API legacyMode argument for Runner status" # The name of the feature to be deprecated announcement_milestone: "15.0" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-05-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: "16.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-1-deprecate-maintainer_note.yml b/data/deprecations/15-1-deprecate-maintainer_note.yml index 9656e62f3db..fc35244827d 100644 --- a/data/deprecations/15-1-deprecate-maintainer_note.yml +++ b/data/deprecations/15-1-deprecate-maintainer_note.yml @@ -1,4 +1,4 @@ -- name: "REST API Runner maintainer_note" # (required) The name of the feature to be deprecated +- title: "REST API Runner maintainer_note" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-06-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-1-jira-github-enterprise-dvcs.yml b/data/deprecations/15-1-jira-github-enterprise-dvcs.yml index d35d06e006c..69606c3dd2d 100644 --- a/data/deprecations/15-1-jira-github-enterprise-dvcs.yml +++ b/data/deprecations/15-1-jira-github-enterprise-dvcs.yml @@ -1,4 +1,4 @@ -- name: "Jira GitHub Enterprise DVCS integration" # The name of the feature to be deprecated +- title: "Jira GitHub Enterprise DVCS integration" # The name of the feature to be deprecated announcement_milestone: "15.1" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-06-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: "16.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml b/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml index bc2df85c1c5..aa6b9ea06db 100644 --- a/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml +++ b/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml @@ -1,4 +1,4 @@ -- name: "PipelineSecurityReportFinding name GraphQL field" # (required) The name of the feature to be deprecated +- title: "PipelineSecurityReportFinding name GraphQL field" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-06-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml b/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml index 511f691f6bb..e127a258f4f 100644 --- a/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml +++ b/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml @@ -1,4 +1,4 @@ -- name: "PipelineSecurityReportFinding projectFingerprint GraphQL field" # (required) The name of the feature to be deprecated +- title: "PipelineSecurityReportFinding projectFingerprint GraphQL field" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-06-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-1-project-pipeline-securityReportFindings.yml b/data/deprecations/15-1-project-pipeline-securityReportFindings.yml index 3d93c94770b..bb46a9b90dd 100644 --- a/data/deprecations/15-1-project-pipeline-securityReportFindings.yml +++ b/data/deprecations/15-1-project-pipeline-securityReportFindings.yml @@ -1,4 +1,4 @@ -- name: "project.pipeline.securityReportFindings GraphQL query" # (required) The name of the feature to be deprecated +- title: "project.pipeline.securityReportFindings GraphQL query" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-06-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml b/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml index 058ff44d618..2bcf1e114b4 100644 --- a/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml +++ b/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml @@ -1,4 +1,4 @@ -- name: "Vulnerability Report sort by State" # (required) The name of the feature to be deprecated +- title: "Vulnerability Report sort by State" # (required) The name of the feature to be deprecated announcement_milestone: "15.0" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-05-22" # (required) 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.3" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-2-job_age-deprecation.yml b/data/deprecations/15-2-job_age-deprecation.yml index b395c97447c..b550f10920e 100644 --- a/data/deprecations/15-2-job_age-deprecation.yml +++ b/data/deprecations/15-2-job_age-deprecation.yml @@ -17,7 +17,7 @@ # # REQUIRED FIELDS # -- name: "Remove `job_age` parameter from `POST /jobs/request` Runner endpoint" # (required) The name of the feature to be deprecated +- title: "Remove `job_age` parameter from `POST /jobs/request` Runner endpoint" # (required) The name of the feature to be deprecated announcement_milestone: "15.2" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-07-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-3-deprecate-redis-5.yml b/data/deprecations/15-3-deprecate-redis-5.yml index d61b1a1c475..b94539061e5 100644 --- a/data/deprecations/15-3-deprecate-redis-5.yml +++ b/data/deprecations/15-3-deprecate-redis-5.yml @@ -1,4 +1,4 @@ -- name: "Redis 5 deprecated" # (required) The name of the feature to be deprecated +- title: "Redis 5 deprecated" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-08-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-3-deprecation-vulnerability-report-tool-sort.yml b/data/deprecations/15-3-deprecation-vulnerability-report-tool-sort.yml index 326070667f2..a3965f7d0cb 100644 --- a/data/deprecations/15-3-deprecation-vulnerability-report-tool-sort.yml +++ b/data/deprecations/15-3-deprecation-vulnerability-report-tool-sort.yml @@ -1,4 +1,4 @@ -- name: "Vulnerability Report sort by Tool" # (required) The name of the feature to be deprecated +- title: "Vulnerability Report sort by Tool" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-06-22" # (required) 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.3" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-3-omniauth-cas3.yml b/data/deprecations/15-3-omniauth-cas3.yml index 156c89ed06b..70290a3fc51 100644 --- a/data/deprecations/15-3-omniauth-cas3.yml +++ b/data/deprecations/15-3-omniauth-cas3.yml @@ -1,7 +1,7 @@ # # REQUIRED FIELDS # -- name: "CAS OmniAuth provider" # (required) The name of the feature to be deprecated +- title: "CAS OmniAuth provider" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-08-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-3-omniauth-crowd.yml b/data/deprecations/15-3-omniauth-crowd.yml index 1f40ae73901..e14b40a1505 100644 --- a/data/deprecations/15-3-omniauth-crowd.yml +++ b/data/deprecations/15-3-omniauth-crowd.yml @@ -1,7 +1,7 @@ # # REQUIRED FIELDS # -- name: "Atlassian Crowd OmniAuth provider" # (required) The name of the feature to be deprecated +- title: "Atlassian Crowd OmniAuth provider" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-08-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-3-pipeline_activity_limit.yml b/data/deprecations/15-3-pipeline_activity_limit.yml index 5cb620e576e..5374e2d7972 100644 --- a/data/deprecations/15-3-pipeline_activity_limit.yml +++ b/data/deprecations/15-3-pipeline_activity_limit.yml @@ -17,7 +17,7 @@ # # REQUIRED FIELDS # -- name: "Maximum number of active pipelines per project limit (`ci_active_pipelines`)" # (required) The name of the feature to be deprecated +- title: "Maximum number of active pipelines per project limit (`ci_active_pipelines`)" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-08-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml b/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml index 25e8a6a2488..691196a892b 100644 --- a/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml +++ b/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml @@ -1,7 +1,7 @@ # # REQUIRED FIELDS # -- name: "Use of `id` field in vulnerabilityFindingDismiss mutation" # (required) The name of the feature to be deprecated +- title: "Use of `id` field in vulnerabilityFindingDismiss mutation" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-08-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-4-confidence-field-in-graphql.yml b/data/deprecations/15-4-confidence-field-in-graphql.yml index da3287eeff9..90e9a452a43 100644 --- a/data/deprecations/15-4-confidence-field-in-graphql.yml +++ b/data/deprecations/15-4-confidence-field-in-graphql.yml @@ -1,4 +1,4 @@ -- name: "Vulnerability confidence field" +- title: "Vulnerability confidence field" announcement_milestone: "15.4" announcement_date: "2022-09-22" removal_milestone: "16.0" diff --git a/data/deprecations/15-4-create-deprecation-draft-quick-action-toggle.yml b/data/deprecations/15-4-create-deprecation-draft-quick-action-toggle.yml index 5d4fb1b5b66..4da311acd41 100644 --- a/data/deprecations/15-4-create-deprecation-draft-quick-action-toggle.yml +++ b/data/deprecations/15-4-create-deprecation-draft-quick-action-toggle.yml @@ -1,4 +1,4 @@ -- name: "Toggle behavior of `/draft` quick action in merge requests" # (required) The name of the feature to be deprecated +- title: "Toggle behavior of `/draft` quick action in merge requests" # (required) The name of the feature to be deprecated announcement_milestone: "15.4" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-09-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-4-cs-docker-variables.yml b/data/deprecations/15-4-cs-docker-variables.yml index 37f2552ac00..9bd0acff5b0 100644 --- a/data/deprecations/15-4-cs-docker-variables.yml +++ b/data/deprecations/15-4-cs-docker-variables.yml @@ -1,4 +1,4 @@ -- name: "Container Scanning variables that reference Docker" +- title: "Container Scanning variables that reference Docker" announcement_milestone: "15.4" announcement_date: "2022-09-22" removal_milestone: "16.0" diff --git a/data/deprecations/15-4-deprecate-bundled-grafana.yml b/data/deprecations/15-4-deprecate-bundled-grafana.yml index b6659e01c42..1a78691c475 100644 --- a/data/deprecations/15-4-deprecate-bundled-grafana.yml +++ b/data/deprecations/15-4-deprecate-bundled-grafana.yml @@ -1,4 +1,4 @@ -- name: "Bundled Grafana deprecated" +- title: "Bundled Grafana deprecated" announcement_milestone: "15.3" announcement_date: "2022-08-22" removal_milestone: "15.4" diff --git a/data/deprecations/15-4-non-expiring-access-tokens.yml b/data/deprecations/15-4-non-expiring-access-tokens.yml index c4becf9ed34..a302c39bde6 100644 --- a/data/deprecations/15-4-non-expiring-access-tokens.yml +++ b/data/deprecations/15-4-non-expiring-access-tokens.yml @@ -1,4 +1,4 @@ -- name: "Non-expiring access tokens" +- title: "Non-expiring access tokens" announcement_milestone: "15.4" announcement_date: "2022-09-22" removal_milestone: "16.0" diff --git a/data/deprecations/15-4-starboard-directive.yml b/data/deprecations/15-4-starboard-directive.yml index 07b7cdf7fd6..e83f240eef4 100644 --- a/data/deprecations/15-4-starboard-directive.yml +++ b/data/deprecations/15-4-starboard-directive.yml @@ -1,4 +1,4 @@ -- name: "Starboard directive in the config for the GitLab Agent for Kubernetes" +- title: "Starboard directive in the config for the GitLab Agent for Kubernetes" announcement_milestone: "15.4" announcement_date: "2022-09-22" removal_milestone: "16.0" diff --git a/data/deprecations/15-5-confidential-field-on-notes.yml b/data/deprecations/15-5-confidential-field-on-notes.yml index 5ec5c3adab9..ad68eecf04e 100644 --- a/data/deprecations/15-5-confidential-field-on-notes.yml +++ b/data/deprecations/15-5-confidential-field-on-notes.yml @@ -1,4 +1,4 @@ -- name: 'GraphQL field `confidential` changed to `internal` on notes' +- title: 'GraphQL field `confidential` changed to `internal` on notes' announcement_milestone: '15.5' announcement_date: '2022-10-22' removal_milestone: '16.0' diff --git a/data/deprecations/15-5-disable-file-type-var-expansion-ci-pipeline.yml b/data/deprecations/15-5-disable-file-type-var-expansion-ci-pipeline.yml index 31b0d9c2dbc..1a367481f94 100644 --- a/data/deprecations/15-5-disable-file-type-var-expansion-ci-pipeline.yml +++ b/data/deprecations/15-5-disable-file-type-var-expansion-ci-pipeline.yml @@ -1,4 +1,4 @@ -- name: "File Type variable expansion in `.gitlab-ci.yml`" # (required) The name of the feature to be deprecated +- title: "File Type variable expansion in `.gitlab-ci.yml`" # (required) The name of the feature to be deprecated announcement_milestone: "15.5" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-10-22" # (required) 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.7" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml b/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml index 949aa40e5ce..56479933f94 100644 --- a/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml +++ b/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml @@ -1,4 +1,4 @@ -- name: "vulnerabilityFindingDismiss GraphQL mutation" +- title: "vulnerabilityFindingDismiss GraphQL mutation" announcement_milestone: "15.5" announcement_date: "2022-10-22" removal_milestone: "16.0" diff --git a/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml b/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml index 3d8d946027f..5690bc0763f 100644 --- a/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml +++ b/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml @@ -1,13 +1,13 @@ -- name: "Configuration fields in GitLab Runner Helm Chart" # (required) The name of the feature to be deprecated +- title: "Configuration fields in GitLab Runner Helm Chart" # (required) The name of the feature to be deprecated announcement_milestone: "15.6" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-11-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_date: "2023-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. breaking_change: true # (required) If this deprecation is a breaking change, set this value to true reporter: ratchade # (required) GitLab username of the person reporting the deprecation - stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/379064 # (required) Link to the deprecation issue in GitLab + stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/379064 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. From GitLab 13.6, users can [specify any runner configuration in the GitLab Runner Helm chart](https://docs.gitlab.com/runner/install/kubernetes.html). When we implemented this feature, we deprecated values in the GitLab Helm Chart configuration that were specific to GitLab Runner. These fields are deprecated and we plan to remove them in v1.0 of the GitLab Runner Helm chart. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. + end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. diff --git a/data/deprecations/15-6-deprecate-merge_status-api-field.yml b/data/deprecations/15-6-deprecate-merge_status-api-field.yml index 55a7cce0b6c..7d7b160d6bd 100644 --- a/data/deprecations/15-6-deprecate-merge_status-api-field.yml +++ b/data/deprecations/15-6-deprecate-merge_status-api-field.yml @@ -1,15 +1,14 @@ -- name: "merge_status API field" # The name of the feature to be deprecated - announcement_milestone: "15.6" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-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: "16.0" # The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # the date of the milestone release when this feature is planned to be removed - breaking_change: true # If this deprecation is a breaking change, set this value to true - body: | # Do not modify this line, instead modify the lines below. +- title: "merge_status API field" + announcement_milestone: "15.6" + announcement_date: "2022-11-22" + removal_milestone: "16.0" + removal_date: "2023-05-22" + breaking_change: true + body: | The `merge_status` field in the [merge request API](https://docs.gitlab.com/ee/api/merge_requests.html#merge-status) has been deprecated in favor of the `detailed_merge_status` field which more correctly identifies all of the potential statuses that a merge request can be in. API users are encouraged to use the new `detailed_merge_status` field instead. The `merge_status` field will be removed in v5 of the GitLab REST API. -# The following items are not published on the docs page, but may be used in the future. - stage: create # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth - tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/382032 # (optional) This is a link to the deprecation issue in GitLab - documentation_url: https://docs.gitlab.com/ee/api/merge_requests.html#merge-status # (optional) This is a link to the current documentation page - image_url: # (optional) This is a link to a thumbnail image depicting the feature - video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg + stage: create + tiers: + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/382032 + documentation_url: https://docs.gitlab.com/ee/api/merge_requests.html#merge-status + image_url: + video_url: diff --git a/data/deprecations/15-6-deprecate-post-api-v4-runner.yml b/data/deprecations/15-6-deprecate-post-api-v4-runner.yml index 9e308fbecce..878b9f4922f 100644 --- a/data/deprecations/15-6-deprecate-post-api-v4-runner.yml +++ b/data/deprecations/15-6-deprecate-post-api-v4-runner.yml @@ -1,11 +1,11 @@ -- name: "`POST /api/v4/runners` method to register runners" # (required) The name of the feature to be deprecated +- title: "`POST /api/v4/runners` method to register runners" # (required) The name of the feature to be deprecated announcement_milestone: "15.6" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-11-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_date: "2023-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. breaking_change: true # (required) If this deprecation is a breaking change, set this value to true reporter: pedropombeiro # (required) GitLab username of the person reporting the deprecation - stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth + stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/379743 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. The `POST` method operation on the `/api/v4/runners` endpoint is deprecated. @@ -19,6 +19,6 @@ [runner registration token](https://docs.gitlab.com/ee/security/token_overview.html#runner-registration-tokens). From GitLab 16.0 and later, the runner registration methods implemented by the new GitLab Runner token architecture will be the only supported methods. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. + end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] documentation_url: https://docs.gitlab.com/ee/api/runners.html#register-a-new-runner # (optional) This is a link to the current documentation page diff --git a/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml b/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml index 330f1b1f39e..ac1320c648b 100644 --- a/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml +++ b/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml @@ -1,12 +1,12 @@ -- name: "`runnerRegistrationToken` parameter for GitLab Runner Helm Chart" # (required) The name of the feature to be deprecated +- title: "`runnerRegistrationToken` parameter for GitLab Runner Helm Chart" # (required) The name of the feature to be deprecated announcement_milestone: "15.6" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-11-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_date: "2023-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. breaking_change: true # (required) If this deprecation is a breaking change, set this value to true reporter: pedropombeiro # (required) GitLab username of the person reporting the deprecation - stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/381111 # (required) Link to the deprecation issue in GitLab + stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/381111 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. The [`runnerRegistrationToken`](https://docs.gitlab.com/runner/install/kubernetes.html#required-configuration) parameter to use the GitLab Helm Chart to install a runner on Kubernetes is deprecated. @@ -16,4 +16,4 @@ - A unique system ID saved to the `config.toml`, which will ensure traceability between jobs and runners. From GitLab 16.0 and later, the methods to register runners introduced by the new GitLab Runner token architecture will be the only supported methods. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. + end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. diff --git a/data/deprecations/15-6-deprecate-runner-register-command.yml b/data/deprecations/15-6-deprecate-runner-register-command.yml index b20bc4bbeec..a3ae01177a1 100644 --- a/data/deprecations/15-6-deprecate-runner-register-command.yml +++ b/data/deprecations/15-6-deprecate-runner-register-command.yml @@ -1,4 +1,4 @@ -- name: "`gitlab-runner register` command" # (required) The name of the feature to be deprecated +- title: "`gitlab-runner register` command" # (required) The name of the feature to be deprecated announcement_milestone: "15.6" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-11-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed diff --git a/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml b/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml index 20f6ba758bb..14e77a5b027 100644 --- a/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml +++ b/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml @@ -1,20 +1,16 @@ -- name: "GitLab Runner registration token in Runner Operator" # (required) The name of the feature to be deprecated +- title: "GitLab Runner registration token in Runner Operator" # (required) The name of the feature to be deprecated announcement_milestone: "15.6" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2022-11-22" # (required) 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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_date: "2023-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. breaking_change: true # (required) If this deprecation is a breaking change, set this value to true - reporter: ratchade # (required) GitLab username of the person reporting the deprecation - stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/382077 # (required) Link to the deprecation issue in GitLab + reporter: ratchade # (required) GitLab username of the person reporting the deprecation + stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/382077 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. The [`runner-registration-token`](https://docs.gitlab.com/runner/install/operator.html#install-the-kubernetes-operator) parameter that uses the OpenShift and k8s Vanilla Operator to install a runner on Kubernetes is deprecated. GitLab plans to introduce a new [GitLab Runner token architecture](https://docs.gitlab.com/ee/architecture/blueprints/runner_tokens/) in GitLab 15.8, which introduces a new method for registering runners and eliminates the legacy runner registration token. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. - - -# OTHER OPTIONAL FIELDS -# + end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] documentation_url: https://docs.gitlab.com/runner/install/operator.html#install-the-kubernetes-operator # (optional) This is a link to the current documentation page image_url: # (optional) This is a link to a thumbnail image depicting the feature diff --git a/data/deprecations/16-0-security_report_schemas_v14-x-x.yml b/data/deprecations/16-0-security_report_schemas_v14-x-x.yml index 46f6012a7db..5001bd490b0 100644 --- a/data/deprecations/16-0-security_report_schemas_v14-x-x.yml +++ b/data/deprecations/16-0-security_report_schemas_v14-x-x.yml @@ -1,7 +1,7 @@ # # REQUIRED FIELDS # -- name: "Security report schemas version 14.x.x" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. +- title: "Security report schemas version 14.x.x" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. announcement_milestone: "15.3" # (required) The milestone when this feature was deprecated. announcement_date: "2022-08-22" # (required) The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "16.0" # (required) The milestone when this feature is being removed. diff --git a/data/deprecations/distribution_deprecations_14-4.yml b/data/deprecations/distribution_deprecations_14-4.yml index e54108d2947..8dc948918c1 100644 --- a/data/deprecations/distribution_deprecations_14-4.yml +++ b/data/deprecations/distribution_deprecations_14-4.yml @@ -1,4 +1,4 @@ -- name: "Move `custom_hooks_dir` setting from GitLab Shell to Gitaly" # The name of the feature to be deprecated +- title: "Move `custom_hooks_dir` setting from GitLab Shell to Gitaly" # The name of the feature to be deprecated announcement_milestone: "14.9" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-03-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/deprecations/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb index b5f58ec0556..7712790d166 100644 --- a/data/deprecations/templates/_deprecation_template.md.erb +++ b/data/deprecations/templates/_deprecation_template.md.erb @@ -53,7 +53,7 @@ sole discretion of GitLab Inc. <%- entries.select{|d| d["announcement_milestone"] == milestone}.each do |deprecation| %> <div class="deprecation removal-<%= deprecation["removal_milestone"].gsub('.', '') %><% if deprecation["breaking_change"] -%> breaking-change<% end %>"> -### <%= deprecation["name"]%> +### <%= deprecation["title"] %> <% if deprecation["end_of_support_milestone"] -%> End of Support: GitLab <span class="removal-milestone"><%= deprecation["end_of_support_milestone"]%></span> (<%= deprecation["end_of_support_date"]%>)<br /> diff --git a/data/deprecations/templates/example.yml b/data/deprecations/templates/example.yml index cc512f70b3e..0109b6e9f13 100644 --- a/data/deprecations/templates/example.yml +++ b/data/deprecations/templates/example.yml @@ -16,7 +16,7 @@ # # REQUIRED FIELDS # -- name: "Feature name" # (required) The name of the feature to be deprecated +- title: "Deprecated in favor of option" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. announcement_milestone: "XX.YY" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "YYYY-MM-DD" # (required) 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: "XX.YY" # (required) The milestone when this feature is planned to be removed @@ -30,6 +30,15 @@ This area supports markdown. Delete this entire comment and replace it with your markdown content. + Deprecations must be actionable. + + Use terms such as "deprecated in favor of" or "use X instead." + + For example: + + - The `confidential` field for a `Note` is deprecated. Use `internal` instead. + - The `merge_status` field in the merge request API has been deprecated in favor of `detailed_merge_status`. + When ready, assign to your tech writer for review. When ready, they will run `bin/rake gitlab:docs:compile_deprecations` to update the deprecations doc, then merge. END OF BODY COMMENT --> diff --git a/data/removals/14_0/14_0-ds-deprecations.yml b/data/removals/14_0/14_0-ds-deprecations.yml index 91da10097ed..ba47a9d1ed4 100644 --- a/data/removals/14_0/14_0-ds-deprecations.yml +++ b/data/removals/14_0/14_0-ds-deprecations.yml @@ -1,4 +1,4 @@ -- name: "Dependency Scanning" +- title: "Dependency Scanning" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: nicoleschwartz diff --git a/data/removals/14_0/14_0-lc-deprecations.yml b/data/removals/14_0/14_0-lc-deprecations.yml index 6322b102ec5..d5d1b6f422b 100644 --- a/data/removals/14_0/14_0-lc-deprecations.yml +++ b/data/removals/14_0/14_0-lc-deprecations.yml @@ -1,4 +1,4 @@ -- name: "License Compliance" +- title: "License Compliance" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: nicoleschwartz diff --git a/data/removals/14_0/change_default_branch_name_to_main.yml b/data/removals/14_0/change_default_branch_name_to_main.yml index 1c47f99870b..30bac5e5bf8 100644 --- a/data/removals/14_0/change_default_branch_name_to_main.yml +++ b/data/removals/14_0/change_default_branch_name_to_main.yml @@ -1,4 +1,4 @@ -- name: "Default branch name for new repositories now `main`" +- title: "Default branch name for new repositories now `main`" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: sarahwaldner diff --git a/data/removals/14_0/create-code-review-draft-wip.yml b/data/removals/14_0/create-code-review-draft-wip.yml index 20eaaf3cd02..aab9f86b711 100644 --- a/data/removals/14_0/create-code-review-draft-wip.yml +++ b/data/removals/14_0/create-code-review-draft-wip.yml @@ -1,4 +1,4 @@ -- name: "WIP merge requests renamed 'draft merge requests'" +- title: "WIP merge requests renamed 'draft merge requests'" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: phikai diff --git a/data/removals/14_0/create-code-review-w-parameter-removal.yml b/data/removals/14_0/create-code-review-w-parameter-removal.yml index 3adec30a1e7..cb10e1a583d 100644 --- a/data/removals/14_0/create-code-review-w-parameter-removal.yml +++ b/data/removals/14_0/create-code-review-w-parameter-removal.yml @@ -1,4 +1,4 @@ -- name: "`?w=1` URL parameter to ignore whitespace changes" +- title: "`?w=1` URL parameter to ignore whitespace changes" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: phikai diff --git a/data/removals/14_0/deprecation_bump_terraform_template_version.yml b/data/removals/14_0/deprecation_bump_terraform_template_version.yml index 201c2efa8aa..3ccba65553d 100644 --- a/data/removals/14_0/deprecation_bump_terraform_template_version.yml +++ b/data/removals/14_0/deprecation_bump_terraform_template_version.yml @@ -1,4 +1,4 @@ -- name: "Terraform template version" +- title: "Terraform template version" removal_date: "2021-06-22" removal_milestone: "14.0" # example issue_url: "" diff --git a/data/removals/14_0/deprecation_manage_access_14_0.yml b/data/removals/14_0/deprecation_manage_access_14_0.yml index 30167d23d60..5de9e31c44e 100644 --- a/data/removals/14_0/deprecation_manage_access_14_0.yml +++ b/data/removals/14_0/deprecation_manage_access_14_0.yml @@ -1,4 +1,4 @@ -- name: Limit projects returned in `GET /groups/:id/` +- title: Limit projects returned in `GET /groups/:id/` removal_date: "2021-06-22" removal_milestone: "14.0" reporter: ogolowisnki @@ -7,7 +7,7 @@ body: | To improve performance, we are limiting the number of projects returned from the `GET /groups/:id/` API call to 100. A complete list of projects can still be retrieved with the `GET /groups/:id/projects` API call. -- name: "GitLab OAuth implicit grant" +- title: "GitLab OAuth implicit grant" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: ogolowinski diff --git a/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml b/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml index 4df59321bc5..d7ac8818476 100644 --- a/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml +++ b/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml @@ -1,4 +1,4 @@ -- name: "Hardcoded `master` in CI/CD templates" +- title: "Hardcoded `master` in CI/CD templates" reporter: dhershkovitch removal_date: "2021-06-22" removal_milestone: "14.0" diff --git a/data/removals/14_0/deuley_servicetemplates_removal.yml b/data/removals/14_0/deuley_servicetemplates_removal.yml index bbc70d98562..4854911b8ac 100644 --- a/data/removals/14_0/deuley_servicetemplates_removal.yml +++ b/data/removals/14_0/deuley_servicetemplates_removal.yml @@ -1,4 +1,4 @@ -- name: "Service Templates" +- title: "Service Templates" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deuley diff --git a/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml b/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml index d7e12a89f14..7f1133f12d0 100644 --- a/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml +++ b/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml @@ -1,4 +1,4 @@ -- name: "Release description in the Tags API" +- title: "Release description in the Tags API" reporter: kbychu removal_date: "2021-06-22" removal_milestone: "14.0" diff --git a/data/removals/14_0/release_deprecation_auto-deploy-image.yml b/data/removals/14_0/release_deprecation_auto-deploy-image.yml index d6cd9ac23ca..b68388e0a9a 100644 --- a/data/removals/14_0/release_deprecation_auto-deploy-image.yml +++ b/data/removals/14_0/release_deprecation_auto-deploy-image.yml @@ -1,4 +1,4 @@ -- name: "Auto Deploy CI template v1" +- title: "Auto Deploy CI template v1" reporter: kbychu removal_date: "2021-06-22" removal_milestone: "14.0" diff --git a/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml b/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml index bb10ab8a2ab..902c36b8e96 100644 --- a/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml +++ b/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml @@ -1,4 +1,4 @@ -- name: "Disk source configuration for GitLab Pages" +- title: "Disk source configuration for GitLab Pages" reporter: kbychu removal_date: "2021-06-22" removal_milestone: "14.0" diff --git a/data/removals/14_0/release_legacy_feature_flags_deprecation.yml b/data/removals/14_0/release_legacy_feature_flags_deprecation.yml index bf0075faa1e..4bf95e4ed35 100644 --- a/data/removals/14_0/release_legacy_feature_flags_deprecation.yml +++ b/data/removals/14_0/release_legacy_feature_flags_deprecation.yml @@ -1,4 +1,4 @@ -- name: "Legacy feature flags" +- title: "Legacy feature flags" reporter: kbychu removal_date: "2021-06-22" removal_milestone: "14.0" diff --git a/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml b/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml index 98aef74fd03..3679242d33a 100644 --- a/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml +++ b/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml @@ -1,4 +1,4 @@ -- name: "Redundant timestamp field from DORA metrics API payload" +- title: "Redundant timestamp field from DORA metrics API payload" reporter: kbychu removal_date: "2021-06-22" removal_milestone: "14.0" diff --git a/data/removals/14_0/removal-geo-fdw-settings.yml b/data/removals/14_0/removal-geo-fdw-settings.yml index 5997705bf30..b2d035921c9 100644 --- a/data/removals/14_0/removal-geo-fdw-settings.yml +++ b/data/removals/14_0/removal-geo-fdw-settings.yml @@ -1,4 +1,4 @@ -- name: "Geo Foreign Data Wrapper settings" +- title: "Geo Foreign Data Wrapper settings" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: fzimmer diff --git a/data/removals/14_0/removal-graphql-fields.yml b/data/removals/14_0/removal-graphql-fields.yml index 71d277bd6fc..bf73c427f96 100644 --- a/data/removals/14_0/removal-graphql-fields.yml +++ b/data/removals/14_0/removal-graphql-fields.yml @@ -1,4 +1,4 @@ -- name: "Deprecated GraphQL fields" +- title: "Deprecated GraphQL fields" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: gweaver diff --git a/data/removals/14_0/removal-legacy-storage.yml b/data/removals/14_0/removal-legacy-storage.yml index 28b6ffeb0d1..4c229c9e9d9 100644 --- a/data/removals/14_0/removal-legacy-storage.yml +++ b/data/removals/14_0/removal-legacy-storage.yml @@ -1,4 +1,4 @@ -- name: "Legacy storage" +- title: "Legacy storage" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: fzimmer diff --git a/data/removals/14_0/removal-protect-features.yml b/data/removals/14_0/removal-protect-features.yml index e8e71f7bbcd..71fcaddaa06 100644 --- a/data/removals/14_0/removal-protect-features.yml +++ b/data/removals/14_0/removal-protect-features.yml @@ -1,4 +1,4 @@ -- name: Container Scanning Engine Clair +- title: Container Scanning Engine Clair removal_date: "2021-06-22" removal_milestone: "14.0" reporter: sam.white @@ -6,7 +6,7 @@ body: | Clair, the default container scanning engine, was deprecated in GitLab 13.9 and is removed from GitLab 14.0 and replaced by Trivy. We advise customers who are customizing variables for their container scanning job to [follow these instructions](https://docs.gitlab.com/ee/user/application_security/container_scanning/#change-scanners) to ensure that their container scanning jobs continue to work. -- name: Web Application Firewall (WAF) +- title: Web Application Firewall (WAF) removal_date: "2021-06-22" removal_milestone: "14.0" reporter: sam.white diff --git a/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml b/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml index d53e7744e3a..bbff9c56dda 100644 --- a/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml +++ b/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml @@ -1,4 +1,4 @@ -- name: Experimental prefix in Sidekiq queue selector options +- title: Experimental prefix in Sidekiq queue selector options removal_date: "2021-06-22" removal_milestone: "14.0" reporter: smcgivern diff --git a/data/removals/14_0/removal-unicorn.yml b/data/removals/14_0/removal-unicorn.yml index d5062aa0eea..737c1fa53aa 100644 --- a/data/removals/14_0/removal-unicorn.yml +++ b/data/removals/14_0/removal-unicorn.yml @@ -1,4 +1,4 @@ -- name: "Unicorn in GitLab self-managed" +- title: "Unicorn in GitLab self-managed" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: fzimmer diff --git a/data/removals/14_0/removal_ci_project_config_path.yml b/data/removals/14_0/removal_ci_project_config_path.yml index d71fbbb78f3..a54722c5923 100644 --- a/data/removals/14_0/removal_ci_project_config_path.yml +++ b/data/removals/14_0/removal_ci_project_config_path.yml @@ -1,4 +1,4 @@ -- name: "`CI_PROJECT_CONFIG_PATH` variable" +- title: "`CI_PROJECT_CONFIG_PATH` variable" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: stkerr diff --git a/data/removals/14_0/removal_enablement_helm2.yml b/data/removals/14_0/removal_enablement_helm2.yml index 09136bead3e..57ed67851c3 100644 --- a/data/removals/14_0/removal_enablement_helm2.yml +++ b/data/removals/14_0/removal_enablement_helm2.yml @@ -1,4 +1,4 @@ -- name: "Helm v2 support" +- title: "Helm v2 support" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: joshlambert diff --git a/data/removals/14_0/removal_enablement_opensuse_15_1.yml b/data/removals/14_0/removal_enablement_opensuse_15_1.yml index 2e0333c3b88..c9da3535f41 100644 --- a/data/removals/14_0/removal_enablement_opensuse_15_1.yml +++ b/data/removals/14_0/removal_enablement_opensuse_15_1.yml @@ -1,4 +1,4 @@ -- name: "OpenSUSE Leap 15.1" +- title: "OpenSUSE Leap 15.1" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: dorrino diff --git a/data/removals/14_0/removal_enablement_pg11.yml b/data/removals/14_0/removal_enablement_pg11.yml index d409a1bc9d3..a7f9d3910be 100644 --- a/data/removals/14_0/removal_enablement_pg11.yml +++ b/data/removals/14_0/removal_enablement_pg11.yml @@ -1,4 +1,4 @@ -- name: "PostgreSQL 11 support" +- title: "PostgreSQL 11 support" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: joshlambert diff --git a/data/removals/14_0/removal_enablement_ubuntu_16.yml b/data/removals/14_0/removal_enablement_ubuntu_16.yml index e67829de7ab..4c345c23e9c 100644 --- a/data/removals/14_0/removal_enablement_ubuntu_16.yml +++ b/data/removals/14_0/removal_enablement_ubuntu_16.yml @@ -1,4 +1,4 @@ -- name: "Ubuntu 16.04 support" +- title: "Ubuntu 16.04 support" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: joshlambert diff --git a/data/removals/14_0/removal_repost_static_analysis_notices.yml b/data/removals/14_0/removal_repost_static_analysis_notices.yml index 1a2ae93a902..6ee59f72c4e 100644 --- a/data/removals/14_0/removal_repost_static_analysis_notices.yml +++ b/data/removals/14_0/removal_repost_static_analysis_notices.yml @@ -1,4 +1,4 @@ -- name: "Migrate from `SAST_DEFAULT_ANALYZERS` to `SAST_EXCLUDED_ANALYZERS`" +- title: "Migrate from `SAST_DEFAULT_ANALYZERS` to `SAST_EXCLUDED_ANALYZERS`" reporter: tmccaslin removal_date: "2021-06-22" removal_milestone: "14.0" @@ -8,7 +8,7 @@ Until GitLab 13.9, if you wanted to avoid running one particular GitLab SAST analyzer, you needed to remove it from the [long string of analyzers in the `SAST.gitlab-ci.yml` file](https://gitlab.com/gitlab-org/gitlab/-/blob/390afc431e7ce1ac253b35beb39f19e49c746bff/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml#L12) and use that to set the [`SAST_DEFAULT_ANALYZERS`](https://docs.gitlab.com/ee/user/application_security/sast/#docker-images) variable in your project's CI file. If you did this, it would exclude you from future new analyzers because this string hard codes the list of analyzers to execute. We avoid this problem by inverting this variable's logic to exclude, rather than choose default analyzers. Beginning with 13.9, [we migrated](https://gitlab.com/gitlab-org/gitlab/-/blob/14fed7a33bfdbd4663d8928e46002a5ef3e3282c/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml#L13) to `SAST_EXCLUDED_ANALYZERS` in our `SAST.gitlab-ci.yml` file. We encourage anyone who uses a [customized SAST configuration](https://docs.gitlab.com/ee/user/application_security/sast/#customizing-the-sast-settings) in their project CI file to migrate to this new variable. If you have not overridden `SAST_DEFAULT_ANALYZERS`, no action is needed. The CI/CD variable `SAST_DEFAULT_ANALYZERS` has been removed in GitLab 14.0, which released on June 22, 2021. -- name: "`secret_detection_default_branch` job" +- title: "`secret_detection_default_branch` job" reporter: tmccaslin removal_date: "2021-06-22" removal_milestone: "14.0" @@ -18,7 +18,7 @@ To ensure Secret Detection was scanning both default branches and feature branches, we introduced two separate secret detection CI jobs (`secret_detection_default_branch` and `secret_detection`) in our managed [`Secret-Detection.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/Secret-Detection.gitlab-ci.yml) template. These two CI jobs created confusion and complexity in the CI rules logic. This deprecation moves the `rule` logic into the `script` section, which then determines how the `secret_detection` job is run (historic, on a branch, commits, etc). If you override or maintain custom versions of `SAST.gitlab-ci.yml` or `Secret-Detection.gitlab-ci.yml`, you must update your CI templates. We strongly encourage [inheriting and overriding our managed CI templates](https://docs.gitlab.com/ee/user/application_security/secret_detection/#custom-settings-example) to future-proof your CI templates. GitLab 14.0 no longer supports the old `secret_detection_default_branch` job. -- name: "SAST analyzer `SAST_GOSEC_CONFIG` variable" +- title: "SAST analyzer `SAST_GOSEC_CONFIG` variable" reporter: tmccaslin removal_date: "2021-06-22" removal_milestone: "14.0" @@ -28,7 +28,7 @@ With the release of [SAST Custom Rulesets](https://docs.gitlab.com/ee/user/application_security/sast/#customize-rulesets) in GitLab 13.5 we allow greater flexibility in configuration options for our Go analyzer (GoSec). As a result we no longer plan to support our less flexible [`SAST_GOSEC_CONFIG`](https://docs.gitlab.com/ee/user/application_security/sast/#analyzer-settings) analyzer setting. This variable was deprecated in GitLab 13.10. GitLab 14.0 removes the old `SAST_GOSEC_CONFIG variable`. If you use or override `SAST_GOSEC_CONFIG` in your CI file, update your SAST CI configuration or pin to an older version of the GoSec analyzer. We strongly encourage [inheriting and overriding our managed CI templates](https://docs.gitlab.com/ee/user/application_security/sast/#overriding-sast-jobs) to future-proof your CI templates. -- name: "Global `SAST_ANALYZER_IMAGE_TAG` in SAST CI template" +- title: "Global `SAST_ANALYZER_IMAGE_TAG` in SAST CI template" reporter: tmccaslin removal_date: "2021-06-22" removal_milestone: "14.0" diff --git a/data/removals/14_0/removal_runner_25555.yml b/data/removals/14_0/removal_runner_25555.yml index f775bd977bf..13c4d41989c 100644 --- a/data/removals/14_0/removal_runner_25555.yml +++ b/data/removals/14_0/removal_runner_25555.yml @@ -1,4 +1,4 @@ -- name: "Off peak time mode configuration for Docker Machine autoscaling" +- title: "Off peak time mode configuration for Docker Machine autoscaling" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removal_runner_26036.yml b/data/removals/14_0/removal_runner_26036.yml index 5f391909a2d..c806b2b54f1 100644 --- a/data/removals/14_0/removal_runner_26036.yml +++ b/data/removals/14_0/removal_runner_26036.yml @@ -1,4 +1,4 @@ -- name: "Ubuntu 19.10 (Eoan Ermine) package" +- title: "Ubuntu 19.10 (Eoan Ermine) package" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removal_runner_26419.yml b/data/removals/14_0/removal_runner_26419.yml index 85d57de763e..83690f807ba 100644 --- a/data/removals/14_0/removal_runner_26419.yml +++ b/data/removals/14_0/removal_runner_26419.yml @@ -1,4 +1,4 @@ -- name: "Make `pwsh` the default shell for newly-registered Windows Runners" +- title: "Make `pwsh` the default shell for newly-registered Windows Runners" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removal_runner_4845.yml b/data/removals/14_0/removal_runner_4845.yml index db25c0741cb..7aab67e3d41 100644 --- a/data/removals/14_0/removal_runner_4845.yml +++ b/data/removals/14_0/removal_runner_4845.yml @@ -1,4 +1,4 @@ -- name: "GitLab Runner installation to ignore the `skel` directory" +- title: "GitLab Runner installation to ignore the `skel` directory" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removal_runner_6413.yml b/data/removals/14_0/removal_runner_6413.yml index 514cb254d8d..e511b792fe7 100644 --- a/data/removals/14_0/removal_runner_6413.yml +++ b/data/removals/14_0/removal_runner_6413.yml @@ -1,4 +1,4 @@ -- name: "`FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL` feature flag" +- title: "`FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL` feature flag" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removals-14-testing-team.yml b/data/removals/14_0/removals-14-testing-team.yml index 8b877ece6cc..4146bfe916c 100644 --- a/data/removals/14_0/removals-14-testing-team.yml +++ b/data/removals/14_0/removals-14-testing-team.yml @@ -1,4 +1,4 @@ -- name: "Default Browser Performance testing job renamed in GitLab 14.0" +- title: "Default Browser Performance testing job renamed in GitLab 14.0" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: jheimbuck_gl @@ -7,7 +7,7 @@ Browser Performance Testing has run in a job named `performance` by default. With the introduction of [Load Performance Testing](https://docs.gitlab.com/ee/ci/testing/code_quality.html) in GitLab 13.2, this naming could be confusing. To make it clear which job is running [Browser Performance Testing](https://docs.gitlab.com/ee/ci/testing/browser_performance_testing.html), the default job name is changed from `performance` to `browser_performance` in the template in GitLab 14.0. Relevant Issue: [Rename default Browser Performance Testing job](https://gitlab.com/gitlab-org/gitlab/-/issues/225914) -- name: "Code Quality RuboCop support changed" +- title: "Code Quality RuboCop support changed" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: jheimbuck_gl @@ -16,7 +16,7 @@ By default, the Code Quality feature has not provided support for Ruby 2.6+ if you're using the Code Quality template. To better support the latest versions of Ruby, the default RuboCop version is updated to add support for Ruby 2.4 through 3.0. As a result, support for Ruby 2.1, 2.2, and 2.3 is removed. You can re-enable support for older versions by [customizing your configuration](https://docs.gitlab.com/ee/ci/testing/code_quality.html#rubocop-errors). Relevant Issue: [Default `codeclimate-rubocop` engine does not support Ruby 2.6+](https://gitlab.com/gitlab-org/ci-cd/codequality/-/issues/28) -- name: "Ruby version changed in `Ruby.gitlab-ci.yml`" +- title: "Ruby version changed in `Ruby.gitlab-ci.yml`" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: jheimbuck_gl diff --git a/data/removals/14_0/removals_runner_26651.yml b/data/removals/14_0/removals_runner_26651.yml index 8a35996c81a..c2c0f88728a 100644 --- a/data/removals/14_0/removals_runner_26651.yml +++ b/data/removals/14_0/removals_runner_26651.yml @@ -1,4 +1,4 @@ -- name: "`/usr/lib/gitlab-runner` symlink from package" +- title: "`/usr/lib/gitlab-runner` symlink from package" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removals_runner_26679.yml b/data/removals/14_0/removals_runner_26679.yml index e99a551a293..1827992a801 100644 --- a/data/removals/14_0/removals_runner_26679.yml +++ b/data/removals/14_0/removals_runner_26679.yml @@ -1,4 +1,4 @@ -- name: "`FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag" +- title: "`FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removals_runner_26900.yml b/data/removals/14_0/removals_runner_26900.yml index addf11c86ad..a823d797c1a 100644 --- a/data/removals/14_0/removals_runner_26900.yml +++ b/data/removals/14_0/removals_runner_26900.yml @@ -1,4 +1,4 @@ -- name: "Success and failure for finished build metric conversion" +- title: "Success and failure for finished build metric conversion" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removals_runner_27175.yml b/data/removals/14_0/removals_runner_27175.yml index a31c4e757e7..c164f50a973 100644 --- a/data/removals/14_0/removals_runner_27175.yml +++ b/data/removals/14_0/removals_runner_27175.yml @@ -1,4 +1,4 @@ -- name: "`FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag" +- title: "`FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removals_runner_27218.yml b/data/removals/14_0/removals_runner_27218.yml index 8fb7e800b0b..8c18551d68b 100644 --- a/data/removals/14_0/removals_runner_27218.yml +++ b/data/removals/14_0/removals_runner_27218.yml @@ -1,4 +1,4 @@ -- name: "GitLab Runner helper image in GitLab.com Container Registry" +- title: "GitLab Runner helper image in GitLab.com Container Registry" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removals_runner_27551.yml b/data/removals/14_0/removals_runner_27551.yml index 43ecf3d72f6..0165a541420 100644 --- a/data/removals/14_0/removals_runner_27551.yml +++ b/data/removals/14_0/removals_runner_27551.yml @@ -1,4 +1,4 @@ -- name: "Windows Server 1903 image support" +- title: "Windows Server 1903 image support" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/removals_runner_27899.yml b/data/removals/14_0/removals_runner_27899.yml index 468e04dc677..8eef3009df8 100644 --- a/data/removals/14_0/removals_runner_27899.yml +++ b/data/removals/14_0/removals_runner_27899.yml @@ -1,4 +1,4 @@ -- name: "Windows Server 1909 image support" +- title: "Windows Server 1909 image support" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman diff --git a/data/removals/14_0/remove-sql-elector.yml b/data/removals/14_0/remove-sql-elector.yml index 6a306569d9f..2628f23129c 100644 --- a/data/removals/14_0/remove-sql-elector.yml +++ b/data/removals/14_0/remove-sql-elector.yml @@ -1,4 +1,4 @@ -- name: "Gitaly Cluster SQL primary elector" +- title: "Gitaly Cluster SQL primary elector" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: mjwood diff --git a/data/removals/14_0/remove_dast_env_variables.yml b/data/removals/14_0/remove_dast_env_variables.yml index 3a40c6518e0..8ed23aae6fa 100644 --- a/data/removals/14_0/remove_dast_env_variables.yml +++ b/data/removals/14_0/remove_dast_env_variables.yml @@ -1,4 +1,4 @@ -- name: "DAST environment variable renaming and removal" +- title: "DAST environment variable renaming and removal" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: derekferguson diff --git a/data/removals/14_0/remove_dast_legacy_domain_validation.yml b/data/removals/14_0/remove_dast_legacy_domain_validation.yml index 39acc3e7188..ffb2ec1118e 100644 --- a/data/removals/14_0/remove_dast_legacy_domain_validation.yml +++ b/data/removals/14_0/remove_dast_legacy_domain_validation.yml @@ -1,4 +1,4 @@ -- name: "Legacy DAST domain validation" +- title: "Legacy DAST domain validation" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: derekferguson diff --git a/data/removals/14_0/remove_dast_legacy_report_fields.yml b/data/removals/14_0/remove_dast_legacy_report_fields.yml index e5fca1fa256..cf885ca521d 100644 --- a/data/removals/14_0/remove_dast_legacy_report_fields.yml +++ b/data/removals/14_0/remove_dast_legacy_report_fields.yml @@ -1,4 +1,4 @@ -- name: "Legacy fields from DAST report" +- title: "Legacy fields from DAST report" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: derekferguson diff --git a/data/removals/14_0/remove_dast_spider_host_reset.yml b/data/removals/14_0/remove_dast_spider_host_reset.yml index 53122f6071f..6a44a70655e 100644 --- a/data/removals/14_0/remove_dast_spider_host_reset.yml +++ b/data/removals/14_0/remove_dast_spider_host_reset.yml @@ -1,4 +1,4 @@ -- name: "Default DAST spider begins crawling at target URL" +- title: "Default DAST spider begins crawling at target URL" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: derekferguson diff --git a/data/removals/14_0/remove_dast_template_stages.yml b/data/removals/14_0/remove_dast_template_stages.yml index 0995e09c3ed..4a7c9f13fc8 100644 --- a/data/removals/14_0/remove_dast_template_stages.yml +++ b/data/removals/14_0/remove_dast_template_stages.yml @@ -1,4 +1,4 @@ -- name: "DAST default template stages" +- title: "DAST default template stages" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: derekferguson diff --git a/data/removals/14_0/remove_optimize_api.yml b/data/removals/14_0/remove_optimize_api.yml index a472e6a0d59..aa50a4ce7d2 100644 --- a/data/removals/14_0/remove_optimize_api.yml +++ b/data/removals/14_0/remove_optimize_api.yml @@ -1,4 +1,4 @@ -- name: "DevOps Adoption API Segments" +- title: "DevOps Adoption API Segments" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: ljlane diff --git a/data/removals/14_0/remove_terraform_template.yml b/data/removals/14_0/remove_terraform_template.yml index 2d78eb1f59c..77fade19fc5 100644 --- a/data/removals/14_0/remove_terraform_template.yml +++ b/data/removals/14_0/remove_terraform_template.yml @@ -1,4 +1,4 @@ -- name: "Breaking changes to Terraform CI template" +- title: "Breaking changes to Terraform CI template" reporter: nagyv-gitlab removal_date: "2021-06-22" removal_milestone: "14.0" diff --git a/data/removals/14_0/verify-ci-removal-parametertrace.yml b/data/removals/14_0/verify-ci-removal-parametertrace.yml index 8822abaf357..7dd74bac53c 100644 --- a/data/removals/14_0/verify-ci-removal-parametertrace.yml +++ b/data/removals/14_0/verify-ci-removal-parametertrace.yml @@ -1,4 +1,4 @@ -- name: "`trace` parameter in `jobs` API" +- title: "`trace` parameter in `jobs` API" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: jreporter diff --git a/data/removals/14_0/verify-ci-removalpipelineservice.yml b/data/removals/14_0/verify-ci-removalpipelineservice.yml index fe3d3f224d1..74c10f8fbbe 100644 --- a/data/removals/14_0/verify-ci-removalpipelineservice.yml +++ b/data/removals/14_0/verify-ci-removalpipelineservice.yml @@ -1,4 +1,4 @@ -- name: "External Pipeline Validation Service Code Changes" +- title: "External Pipeline Validation Service Code Changes" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: jreporter diff --git a/data/removals/14_1/removal-memory-prometheus-options-source.yml b/data/removals/14_1/removal-memory-prometheus-options-source.yml index 57a5dfa5d69..a98dc74bbaf 100644 --- a/data/removals/14_1/removal-memory-prometheus-options-source.yml +++ b/data/removals/14_1/removal-memory-prometheus-options-source.yml @@ -1,4 +1,4 @@ -- name: "Remove support for `prometheus.listen_address` and `prometheus.enable`" +- title: "Remove support for `prometheus.listen_address` and `prometheus.enable`" removal_date: July 22, 2021 removal_milestone: "14.1" reporter: fzimmer diff --git a/data/removals/14_1/removal-outdated-browser-support.yml b/data/removals/14_1/removal-outdated-browser-support.yml index 281b8d65686..8ef732564a8 100644 --- a/data/removals/14_1/removal-outdated-browser-support.yml +++ b/data/removals/14_1/removal-outdated-browser-support.yml @@ -1,4 +1,4 @@ -- name: "Remove support for older browsers" +- title: "Remove support for older browsers" removal_date: July 22, 2021 removal_milestone: "14.1" reporter: leipert diff --git a/data/removals/14_10/14-10-package-permissions-composer-change.yml b/data/removals/14_10/14-10-package-permissions-composer-change.yml index e44f1c55167..47e1502c466 100644 --- a/data/removals/14_10/14-10-package-permissions-composer-change.yml +++ b/data/removals/14_10/14-10-package-permissions-composer-change.yml @@ -1,4 +1,4 @@ -- name: "Permissions change for downloading Composer dependencies" +- title: "Permissions change for downloading Composer dependencies" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "14.10" diff --git a/data/removals/14_2/removal-verify-build-log.yml b/data/removals/14_2/removal-verify-build-log.yml index f80971b6f4d..8ef41231543 100644 --- a/data/removals/14_2/removal-verify-build-log.yml +++ b/data/removals/14_2/removal-verify-build-log.yml @@ -1,4 +1,4 @@ -- name: "Max job log file size of 100 MB" +- title: "Max job log file size of 100 MB" removal_date: August 22, 2021 # day the removal was released removal_milestone: "14.2" reporter: jreporter # GitLab username of the person reporting the removal diff --git a/data/removals/14_3/removal-limit-tags-to-50.yml b/data/removals/14_3/removal-limit-tags-to-50.yml index 24dcddf6955..b75fa440ff6 100644 --- a/data/removals/14_3/removal-limit-tags-to-50.yml +++ b/data/removals/14_3/removal-limit-tags-to-50.yml @@ -1,4 +1,4 @@ -- name: "Introduced limit of 50 tags for jobs" +- title: "Introduced limit of 50 tags for jobs" removal_date: September 22nd, 2021 removal_milestone: "14.3" reporter: jreporter diff --git a/data/removals/14_3/removal-verify-pe-pipelinefindername.yml b/data/removals/14_3/removal-verify-pe-pipelinefindername.yml index e3ad364ce29..ad069308045 100644 --- a/data/removals/14_3/removal-verify-pe-pipelinefindername.yml +++ b/data/removals/14_3/removal-verify-pe-pipelinefindername.yml @@ -1,4 +1,4 @@ -- name: "List project pipelines API endpoint removes `name` support in 14.3" +- title: "List project pipelines API endpoint removes `name` support in 14.3" removal_date: September 22, 2021 # day the removal was released removal_milestone: "14.3" reporter: jreporter # GitLab username of the person reporting the removal diff --git a/data/removals/14_3/removal_legacy_storage_setting.yml b/data/removals/14_3/removal_legacy_storage_setting.yml index 1a635dc9b0a..ded32188e56 100644 --- a/data/removals/14_3/removal_legacy_storage_setting.yml +++ b/data/removals/14_3/removal_legacy_storage_setting.yml @@ -1,4 +1,4 @@ -- name: Use of legacy storage setting +- title: Use of legacy storage setting removal_date: September 22nd, 2021 # day the removal was released removal_milestone: "14.3" reporter: dorrino # GitLab username of the person reporting the removal diff --git a/data/removals/14_6/limit_trigger_pipelines.yml b/data/removals/14_6/limit_trigger_pipelines.yml index 668d887bb0b..f893ebf7643 100644 --- a/data/removals/14_6/limit_trigger_pipelines.yml +++ b/data/removals/14_6/limit_trigger_pipelines.yml @@ -1,4 +1,4 @@ -- name: "Limit the number of triggered pipeline to 25K in free tier" +- title: "Limit the number of triggered pipeline to 25K in free tier" removal_date: Dec 22, 2021 # day the removal was released removal_milestone: "14.6" reporter: dhershkovitch # GitLab username of the person reporting the removal diff --git a/data/removals/14_6/removal-release-cli-s3.yml b/data/removals/14_6/removal-release-cli-s3.yml index 7f37f017431..458c027c4c0 100644 --- a/data/removals/14_6/removal-release-cli-s3.yml +++ b/data/removals/14_6/removal-release-cli-s3.yml @@ -1,4 +1,4 @@ -- name: "Release CLI distributed as a generic package" +- title: "Release CLI distributed as a generic package" removal_date: Dec 22, 2021 # day the removal was released removal_milestone: "14.6" reporter: kbychu # GitLab username of the person reporting the removal diff --git a/data/removals/14_9/removal_monitor_respond_integrated_error_tracking.yml b/data/removals/14_9/removal_monitor_respond_integrated_error_tracking.yml index a0467a56f4f..93824a4e68b 100644 --- a/data/removals/14_9/removal_monitor_respond_integrated_error_tracking.yml +++ b/data/removals/14_9/removal_monitor_respond_integrated_error_tracking.yml @@ -1,4 +1,4 @@ -- name: "Integrated error tracking disabled by default" +- title: "Integrated error tracking disabled by default" announcement_milestone: "14.9" announcement_date: "2022-02-23" # This is the date customers were notified about the change in rate limits, making integrated error tracking unusable, see https://gitlab.com/groups/gitlab-org/-/epics/7580#communication-to-rate-limit-impacted-users removal_milestone: "14.9" diff --git a/data/removals/15_0/15-0-Legacy-approval-status-names-from-License-Compliance-API.yml b/data/removals/15_0/15-0-Legacy-approval-status-names-from-License-Compliance-API.yml index 4a241f913a1..81e9df8d761 100644 --- a/data/removals/15_0/15-0-Legacy-approval-status-names-from-License-Compliance-API.yml +++ b/data/removals/15_0/15-0-Legacy-approval-status-names-from-License-Compliance-API.yml @@ -1,4 +1,4 @@ -- name: "Legacy approval status names in License Compliance API" +- title: "Legacy approval status names in License Compliance API" announcement_milestone: "14.6" announcement_date: "2021-12-13" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-Pseudonymizer.yml b/data/removals/15_0/15-0-Pseudonymizer.yml index f3ad893e5dc..6d0bb6e358c 100644 --- a/data/removals/15_0/15-0-Pseudonymizer.yml +++ b/data/removals/15_0/15-0-Pseudonymizer.yml @@ -1,4 +1,4 @@ -- name: "Pseudonymizer" +- title: "Pseudonymizer" announcement_milestone: "14.7" announcement_date: "2022-01-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-Retire-js-analyzer.yml b/data/removals/15_0/15-0-Retire-js-analyzer.yml index 5b5d38d039c..fa744ca1951 100644 --- a/data/removals/15_0/15-0-Retire-js-analyzer.yml +++ b/data/removals/15_0/15-0-Retire-js-analyzer.yml @@ -1,4 +1,4 @@ -- name: "Retire-JS Dependency Scanning tool" +- title: "Retire-JS Dependency Scanning tool" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-SLES-12-SP2.yml b/data/removals/15_0/15-0-SLES-12-SP2.yml index 40c51fa5f95..b6499455574 100644 --- a/data/removals/15_0/15-0-SLES-12-SP2.yml +++ b/data/removals/15_0/15-0-SLES-12-SP2.yml @@ -1,4 +1,4 @@ -- name: "SUSE Linux Enterprise Server 12 SP2" +- title: "SUSE Linux Enterprise Server 12 SP2" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/removals/15_0/15-0-advanced-search-elasticsearch-6-8.yml b/data/removals/15_0/15-0-advanced-search-elasticsearch-6-8.yml index e40e48ba9e9..d920c54a786 100644 --- a/data/removals/15_0/15-0-advanced-search-elasticsearch-6-8.yml +++ b/data/removals/15_0/15-0-advanced-search-elasticsearch-6-8.yml @@ -1,4 +1,4 @@ -- name: "Elasticsearch 6.8.x in GitLab 15.0" +- title: "Elasticsearch 6.8.x in GitLab 15.0" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-bundler-audit.yml b/data/removals/15_0/15-0-bundler-audit.yml index 991280585ba..397b18580c6 100644 --- a/data/removals/15_0/15-0-bundler-audit.yml +++ b/data/removals/15_0/15-0-bundler-audit.yml @@ -1,4 +1,4 @@ -- name: "bundler-audit Dependency Scanning tool" +- title: "bundler-audit Dependency Scanning tool" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-configure-self-managed-cert-based-kube-feature-flag.yml b/data/removals/15_0/15-0-configure-self-managed-cert-based-kube-feature-flag.yml index a4b8b422dd9..48152a06eb3 100644 --- a/data/removals/15_0/15-0-configure-self-managed-cert-based-kube-feature-flag.yml +++ b/data/removals/15_0/15-0-configure-self-managed-cert-based-kube-feature-flag.yml @@ -1,4 +1,4 @@ -- name: "Self-managed certificate-based integration with Kubernetes feature flagged" +- title: "Self-managed certificate-based integration with Kubernetes feature flagged" announcement_milestone: "14.5" announcement_date: "2021-11-15" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-container-registry-htpasswd.yml b/data/removals/15_0/15-0-container-registry-htpasswd.yml index e9a4b2e9882..78a28c4e615 100644 --- a/data/removals/15_0/15-0-container-registry-htpasswd.yml +++ b/data/removals/15_0/15-0-container-registry-htpasswd.yml @@ -1,4 +1,4 @@ -- name: "Container registry authentication with htpasswd" +- title: "Container registry authentication with htpasswd" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-custom_hooks_dir.yml b/data/removals/15_0/15-0-custom_hooks_dir.yml index 2c116a55e1c..55f63c9bef7 100644 --- a/data/removals/15_0/15-0-custom_hooks_dir.yml +++ b/data/removals/15_0/15-0-custom_hooks_dir.yml @@ -1,4 +1,4 @@ -- name: "Move `custom_hooks_dir` setting from GitLab Shell to Gitaly" +- title: "Move `custom_hooks_dir` setting from GitLab Shell to Gitaly" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-database-deprecate-legacy-database-conf.yml b/data/removals/15_0/15-0-database-deprecate-legacy-database-conf.yml index 37595f8808d..4b203b61649 100644 --- a/data/removals/15_0/15-0-database-deprecate-legacy-database-conf.yml +++ b/data/removals/15_0/15-0-database-deprecate-legacy-database-conf.yml @@ -1,4 +1,4 @@ -- name: "Support for legacy format of `config/database.yml`" +- title: "Support for legacy format of `config/database.yml`" announcement_milestone: "14.3" announcement_date: "2021-09-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-dependency-scanning-default-java-version.yml b/data/removals/15_0/15-0-dependency-scanning-default-java-version.yml index dee3b5093fc..8576b1e0deb 100644 --- a/data/removals/15_0/15-0-dependency-scanning-default-java-version.yml +++ b/data/removals/15_0/15-0-dependency-scanning-default-java-version.yml @@ -1,4 +1,4 @@ -- name: "Dependency Scanning default Java version changed to 17" +- title: "Dependency Scanning default Java version changed to 17" announcement_milestone: "14.10" announcement_date: "2022-04-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-dependency-scanning-python-image.yml b/data/removals/15_0/15-0-dependency-scanning-python-image.yml index cbb1e32a211..1ffd3a4b78e 100644 --- a/data/removals/15_0/15-0-dependency-scanning-python-image.yml +++ b/data/removals/15_0/15-0-dependency-scanning-python-image.yml @@ -1,4 +1,4 @@ -- name: "End of support for Python 3.6 in Dependency Scanning" +- title: "End of support for Python 3.6 in Dependency Scanning" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-ds-default-analyzers.yml b/data/removals/15_0/15-0-ds-default-analyzers.yml index 702ce854d0d..a1cbed6366b 100644 --- a/data/removals/15_0/15-0-ds-default-analyzers.yml +++ b/data/removals/15_0/15-0-ds-default-analyzers.yml @@ -1,4 +1,4 @@ -- name: "DS_DEFAULT_ANALYZERS environment variable" +- title: "DS_DEFAULT_ANALYZERS environment variable" announcement_milestone: "14.0" announcement_date: "2021-06-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-geo-remove-db-rake-tasks.yml b/data/removals/15_0/15-0-geo-remove-db-rake-tasks.yml index 571217f9c92..66d50a7ba67 100644 --- a/data/removals/15_0/15-0-geo-remove-db-rake-tasks.yml +++ b/data/removals/15_0/15-0-geo-remove-db-rake-tasks.yml @@ -1,4 +1,4 @@ -- name: "Custom `geo:db:*` Rake tasks are no longer available" +- title: "Custom `geo:db:*` Rake tasks are no longer available" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-geo-remove-promote-db.yml b/data/removals/15_0/15-0-geo-remove-promote-db.yml index 65fa8fdff8e..73459b04515 100644 --- a/data/removals/15_0/15-0-geo-remove-promote-db.yml +++ b/data/removals/15_0/15-0-geo-remove-promote-db.yml @@ -1,4 +1,4 @@ -- name: "The `promote-db` command is no longer available from `gitlab-ctl`" +- title: "The `promote-db` command is no longer available from `gitlab-ctl`" announcement_milestone: "14.5" announcement_date: "2021-11-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-geo-remove-promote-to-primary-node.yml b/data/removals/15_0/15-0-geo-remove-promote-to-primary-node.yml index 1eb0c1658a2..38e1a87104f 100644 --- a/data/removals/15_0/15-0-geo-remove-promote-to-primary-node.yml +++ b/data/removals/15_0/15-0-geo-remove-promote-to-primary-node.yml @@ -1,4 +1,4 @@ -- name: "`promote-to-primary-node` command from `gitlab-ctl`" +- title: "`promote-to-primary-node` command from `gitlab-ctl`" announcement_milestone: "14.5" announcement_date: "2021-11-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-gitaly-internal-socket-dir.yml b/data/removals/15_0/15-0-gitaly-internal-socket-dir.yml index eedb50d2205..509d034263c 100644 --- a/data/removals/15_0/15-0-gitaly-internal-socket-dir.yml +++ b/data/removals/15_0/15-0-gitaly-internal-socket-dir.yml @@ -1,4 +1,4 @@ -- name: "Support for `gitaly['internal_socket_dir']`" +- title: "Support for `gitaly['internal_socket_dir']`" announcement_milestone: "14.10" announcement_date: "2022-04-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-managed-cluster-applications.yml b/data/removals/15_0/15-0-managed-cluster-applications.yml index b0e4bae8852..74fd72d5d2d 100644 --- a/data/removals/15_0/15-0-managed-cluster-applications.yml +++ b/data/removals/15_0/15-0-managed-cluster-applications.yml @@ -1,4 +1,4 @@ -- name: "`Managed-Cluster-Applications.gitlab-ci.yml`" +- title: "`Managed-Cluster-Applications.gitlab-ci.yml`" announcement_milestone: "14.0" announcement_date: "2021-06-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-merge-commit-message.yml b/data/removals/15_0/15-0-merge-commit-message.yml index ff6acd62304..5e2f82f1fa0 100644 --- a/data/removals/15_0/15-0-merge-commit-message.yml +++ b/data/removals/15_0/15-0-merge-commit-message.yml @@ -1,4 +1,4 @@ -- name: "`defaultMergeCommitMessageWithDescription` GraphQL API field" +- title: "`defaultMergeCommitMessageWithDescription` GraphQL API field" 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 diff --git a/data/removals/15_0/15-0-oauth-implicit-grant.yml b/data/removals/15_0/15-0-oauth-implicit-grant.yml index 4a8cd53dc13..73e4fdae0f5 100644 --- a/data/removals/15_0/15-0-oauth-implicit-grant.yml +++ b/data/removals/15_0/15-0-oauth-implicit-grant.yml @@ -1,4 +1,4 @@ -- name: "OAuth implicit grant" # the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. +- title: "OAuth implicit grant" # the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. announcement_milestone: "14.0" # The milestone when this feature was deprecated. announcement_date: "2021-06-22" # The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is being removed. diff --git a/data/removals/15_0/15-0-oauth-tokens-no-expiry.yml b/data/removals/15_0/15-0-oauth-tokens-no-expiry.yml index f93b8253ec7..54f60cc64d2 100644 --- a/data/removals/15_0/15-0-oauth-tokens-no-expiry.yml +++ b/data/removals/15_0/15-0-oauth-tokens-no-expiry.yml @@ -1,4 +1,4 @@ -- name: "OAuth tokens without an expiration" +- title: "OAuth tokens without an expiration" announcement_milestone: "14.3" announcement_date: "2021-09-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-omniauth-kerberos-gem.yml b/data/removals/15_0/15-0-omniauth-kerberos-gem.yml index fa005ff0404..cf8e9b8ea50 100644 --- a/data/removals/15_0/15-0-omniauth-kerberos-gem.yml +++ b/data/removals/15_0/15-0-omniauth-kerberos-gem.yml @@ -1,4 +1,4 @@ -- name: "`omniauth-kerberos` gem" # the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. +- title: "`omniauth-kerberos` gem" # the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. announcement_milestone: "14.3" # The milestone when this feature was deprecated. announcement_date: "2021-09-22" # The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is being removed. diff --git a/data/removals/15_0/15-0-package-container-registry-group-api.yml b/data/removals/15_0/15-0-package-container-registry-group-api.yml index 4d992c6c75f..0adba1afa0b 100644 --- a/data/removals/15_0/15-0-package-container-registry-group-api.yml +++ b/data/removals/15_0/15-0-package-container-registry-group-api.yml @@ -1,4 +1,4 @@ -- name: "Update to the Container Registry group-level API" +- title: "Update to the Container Registry group-level API" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/removals/15_0/15-0-package-settings-permissions.yml b/data/removals/15_0/15-0-package-settings-permissions.yml index 5a458b588b8..0c649439459 100644 --- a/data/removals/15_0/15-0-package-settings-permissions.yml +++ b/data/removals/15_0/15-0-package-settings-permissions.yml @@ -1,4 +1,4 @@ -- name: "GraphQL permissions change for Package settings" +- title: "GraphQL permissions change for Package settings" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-praefect-database-no-proxy.yml b/data/removals/15_0/15-0-praefect-database-no-proxy.yml index b363decc68e..d25eda37612 100644 --- a/data/removals/15_0/15-0-praefect-database-no-proxy.yml +++ b/data/removals/15_0/15-0-praefect-database-no-proxy.yml @@ -1,4 +1,4 @@ -- name: "Move Gitaly Cluster Praefect `database_host_no_proxy` and `database_port_no_proxy configs`" +- title: "Move Gitaly Cluster Praefect `database_host_no_proxy` and `database_port_no_proxy configs`" announcement_milestone: "14.0" announcement_date: "2021-05-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-praefect-virtual-storage.yml b/data/removals/15_0/15-0-praefect-virtual-storage.yml index a1ffa20bcfd..2b37a324001 100644 --- a/data/removals/15_0/15-0-praefect-virtual-storage.yml +++ b/data/removals/15_0/15-0-praefect-virtual-storage.yml @@ -1,4 +1,4 @@ -- name: "Gitaly nodes in virtual storage" +- title: "Gitaly nodes in virtual storage" announcement_milestone: "13.12" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-04-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/removals/15_0/15-0-protect-cns-chs.yml b/data/removals/15_0/15-0-protect-cns-chs.yml index 470f809efa1..bdf509dba33 100644 --- a/data/removals/15_0/15-0-protect-cns-chs.yml +++ b/data/removals/15_0/15-0-protect-cns-chs.yml @@ -1,4 +1,4 @@ -- name: "Container Network and Host Security" +- title: "Container Network and Host Security" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-protect-vulnerability-check.yml b/data/removals/15_0/15-0-protect-vulnerability-check.yml index 91052457612..dc448f3fb54 100644 --- a/data/removals/15_0/15-0-protect-vulnerability-check.yml +++ b/data/removals/15_0/15-0-protect-vulnerability-check.yml @@ -1,4 +1,4 @@ -- name: "Vulnerability Check" +- title: "Vulnerability Check" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-removal-artifacts-keyword.yml b/data/removals/15_0/15-0-removal-artifacts-keyword.yml index 15c9a5ee27a..6f5eb4804d7 100644 --- a/data/removals/15_0/15-0-removal-artifacts-keyword.yml +++ b/data/removals/15_0/15-0-removal-artifacts-keyword.yml @@ -1,4 +1,4 @@ -- name: "`artifacts:reports:cobertura` keyword" +- title: "`artifacts:reports:cobertura` keyword" announcement_milestone: "14.7" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-removal-testcoveragesetting.yml b/data/removals/15_0/15-0-removal-testcoveragesetting.yml index bd72a28f0db..67dd7aed8ce 100644 --- a/data/removals/15_0/15-0-removal-testcoveragesetting.yml +++ b/data/removals/15_0/15-0-removal-testcoveragesetting.yml @@ -1,4 +1,4 @@ -- name: "Test coverage project CI/CD setting" # The headline announcing the removal. i.e. "`CI_PROJECT_CONFIG_PATH` removed in Gitlab 14.0" +- title: "Test coverage project CI/CD setting" # The headline announcing the removal. i.e. "`CI_PROJECT_CONFIG_PATH` removed in Gitlab 14.0" announcement_milestone: "14.8" # The milestone when this feature was deprecated. announcement_date: "2022-03-22" # The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is being removed. diff --git a/data/removals/15_0/15-0-remove-background-upload-object-storage.yml b/data/removals/15_0/15-0-remove-background-upload-object-storage.yml index dac96032359..ca9fcc408ba 100644 --- a/data/removals/15_0/15-0-remove-background-upload-object-storage.yml +++ b/data/removals/15_0/15-0-remove-background-upload-object-storage.yml @@ -1,4 +1,4 @@ -- name: "Background upload for object storage" +- title: "Background upload for object storage" announcement_milestone: "14.9" announcement_date: "2022-03-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-remove-dependency-proxy-feature-flag.yml b/data/removals/15_0/15-0-remove-dependency-proxy-feature-flag.yml index 577789e7fd2..f8f1cd62966 100644 --- a/data/removals/15_0/15-0-remove-dependency-proxy-feature-flag.yml +++ b/data/removals/15_0/15-0-remove-dependency-proxy-feature-flag.yml @@ -1,4 +1,4 @@ -- name: "`dependency_proxy_for_private_groups` feature flag" # The name of the feature to be deprecated +- title: "`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 diff --git a/data/removals/15_0/15-0-remove-replicaiton-detail-routes.yml b/data/removals/15_0/15-0-remove-replicaiton-detail-routes.yml index 133a7464a91..59775a66534 100644 --- a/data/removals/15_0/15-0-remove-replicaiton-detail-routes.yml +++ b/data/removals/15_0/15-0-remove-replicaiton-detail-routes.yml @@ -1,4 +1,4 @@ -- name: "Legacy Geo Admin UI routes" +- title: "Legacy Geo Admin UI routes" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-remove-versions-packagetype.yml b/data/removals/15_0/15-0-remove-versions-packagetype.yml index de45444b64a..0e1155d3067 100644 --- a/data/removals/15_0/15-0-remove-versions-packagetype.yml +++ b/data/removals/15_0/15-0-remove-versions-packagetype.yml @@ -1,4 +1,4 @@ -- name: "Versions from `PackageType`" +- title: "Versions from `PackageType`" 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 diff --git a/data/removals/15_0/15-0-remove_ff_push_rules_supersede_code_owners.yml b/data/removals/15_0/15-0-remove_ff_push_rules_supersede_code_owners.yml index 61a482fe73f..777152ef1d8 100644 --- a/data/removals/15_0/15-0-remove_ff_push_rules_supersede_code_owners.yml +++ b/data/removals/15_0/15-0-remove_ff_push_rules_supersede_code_owners.yml @@ -1,4 +1,4 @@ -- name: "`push_rules_supersede_code_owners` feature flag" # The name of the feature to be deprecated +- title: "`push_rules_supersede_code_owners` feature flag" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-02-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 diff --git a/data/removals/15_0/15-0-request-profiling.yml b/data/removals/15_0/15-0-request-profiling.yml index f5cea4e0d11..16f4f09e1c1 100644 --- a/data/removals/15_0/15-0-request-profiling.yml +++ b/data/removals/15_0/15-0-request-profiling.yml @@ -1,4 +1,4 @@ -- name: "Request profiling" +- title: "Request profiling" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-runner-api-status-renames-not_connected.yml b/data/removals/15_0/15-0-runner-api-status-renames-not_connected.yml index 9406936a2eb..32de20469bf 100644 --- a/data/removals/15_0/15-0-runner-api-status-renames-not_connected.yml +++ b/data/removals/15_0/15-0-runner-api-status-renames-not_connected.yml @@ -1,4 +1,4 @@ -- name: "Runner status `not_connected` API value" +- title: "Runner status `not_connected` API value" announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. removal_milestone: "15.0" # the milestone when this feature is planned to be removed removal_date: "2022-05-22" diff --git a/data/removals/15_0/15-0-runner-disable-strict-host-key-check.yml b/data/removals/15_0/15-0-runner-disable-strict-host-key-check.yml index 384d025ad66..a8ec1080766 100644 --- a/data/removals/15_0/15-0-runner-disable-strict-host-key-check.yml +++ b/data/removals/15_0/15-0-runner-disable-strict-host-key-check.yml @@ -1,4 +1,4 @@ -- name: "Known host required for GitLab Runner SSH executor" +- title: "Known host required for GitLab Runner SSH executor" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. removal_milestone: "15.0" # the milestone when this feature is planned to be removed removal_date: "2022-05-22" diff --git a/data/removals/15_0/15-0-runner_api_new_stale_status_breaking_change.yml b/data/removals/15_0/15-0-runner_api_new_stale_status_breaking_change.yml index 182c492f17b..1d4c79bc40e 100644 --- a/data/removals/15_0/15-0-runner_api_new_stale_status_breaking_change.yml +++ b/data/removals/15_0/15-0-runner_api_new_stale_status_breaking_change.yml @@ -1,4 +1,4 @@ -- name: "API: `stale` status returned instead of `offline` or `not_connected`" +- title: "API: `stale` status returned instead of `offline` or `not_connected`" announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-12-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/removals/15_0/15-0-sast-dotnet-21.yml b/data/removals/15_0/15-0-sast-dotnet-21.yml index 28f13949154..8c1bf5dfcae 100644 --- a/data/removals/15_0/15-0-sast-dotnet-21.yml +++ b/data/removals/15_0/15-0-sast-dotnet-21.yml @@ -1,4 +1,4 @@ -- name: "SAST support for .NET 2.1" +- title: "SAST support for .NET 2.1" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-sast-spotbugs-java-8.yml b/data/removals/15_0/15-0-sast-spotbugs-java-8.yml index c6e59bf4b0f..1a636cf15e3 100644 --- a/data/removals/15_0/15-0-sast-spotbugs-java-8.yml +++ b/data/removals/15_0/15-0-sast-spotbugs-java-8.yml @@ -1,4 +1,4 @@ -- name: "Out-of-the-box SAST (SpotBugs) support for Java 8" +- title: "Out-of-the-box SAST (SpotBugs) support for Java 8" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-secret-detection-configurations.yml b/data/removals/15_0/15-0-secret-detection-configurations.yml index 0f759fae11c..1bdecd49118 100644 --- a/data/removals/15_0/15-0-secret-detection-configurations.yml +++ b/data/removals/15_0/15-0-secret-detection-configurations.yml @@ -1,4 +1,4 @@ -- name: "Secret Detection configuration variables" +- title: "Secret Detection configuration variables" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-serverless.yml b/data/removals/15_0/15-0-serverless.yml index 9f6a94037d8..ed517e6808c 100644 --- a/data/removals/15_0/15-0-serverless.yml +++ b/data/removals/15_0/15-0-serverless.yml @@ -1,4 +1,4 @@ -- name: "GitLab Serverless" +- title: "GitLab Serverless" announcement_milestone: "14.3" announcement_date: "2021-09-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-sidekiq-metrics-health-check-config.yml b/data/removals/15_0/15-0-sidekiq-metrics-health-check-config.yml index cfd0d5f5b13..efe8636143f 100644 --- a/data/removals/15_0/15-0-sidekiq-metrics-health-check-config.yml +++ b/data/removals/15_0/15-0-sidekiq-metrics-health-check-config.yml @@ -1,4 +1,4 @@ -- name: "Sidekiq configuration for metrics and health checks" +- title: "Sidekiq configuration for metrics and health checks" announcement_milestone: "14.7" announcement_date: "2021-01-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15-0-static-site-editor.yml b/data/removals/15_0/15-0-static-site-editor.yml index bea1b14232a..5ea43041734 100644 --- a/data/removals/15_0/15-0-static-site-editor.yml +++ b/data/removals/15_0/15-0-static-site-editor.yml @@ -1,4 +1,4 @@ -- name: "Static Site Editor" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. +- title: "Static Site Editor" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. announcement_milestone: "14.7" # (required) The milestone when this feature was deprecated. announcement_date: "2022-01-22" # (required) The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "15.0" # (required) The milestone when this feature is being removed. diff --git a/data/removals/15_0/15-0-tracing.yml b/data/removals/15_0/15-0-tracing.yml index 1e99bd4cb3c..fdda6d8faaf 100644 --- a/data/removals/15_0/15-0-tracing.yml +++ b/data/removals/15_0/15-0-tracing.yml @@ -1,4 +1,4 @@ -- name: "Jaeger integration" # The headline announcing the removal. i.e. "`CI_PROJECT_CONFIG_PATH` removed in Gitlab 14.0" +- title: "Jaeger integration" # The headline announcing the removal. i.e. "`CI_PROJECT_CONFIG_PATH` removed in Gitlab 14.0" announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-22" removal_milestone: "15.0" # The milestone when this feature is being removed. diff --git a/data/removals/15_0/15-0-type.yml b/data/removals/15_0/15-0-type.yml index c80efadc008..184bd6fb2e6 100644 --- a/data/removals/15_0/15-0-type.yml +++ b/data/removals/15_0/15-0-type.yml @@ -1,4 +1,4 @@ -- name: "`type` and `types` keyword from CI/CD configuration" +- title: "`type` and `types` keyword from CI/CD configuration" announcement_milestone: "14.6" announcement_date: "2021-12-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/15_0-logging.yml b/data/removals/15_0/15_0-logging.yml index 984ffbb0917..5db77a90b78 100644 --- a/data/removals/15_0/15_0-logging.yml +++ b/data/removals/15_0/15_0-logging.yml @@ -1,4 +1,4 @@ -- name: "ELK stack logging" # The headline announcing the removal. i.e. "`CI_PROJECT_CONFIG_PATH` removed in Gitlab 14.0" +- title: "ELK stack logging" # The headline announcing the removal. i.e. "`CI_PROJECT_CONFIG_PATH` removed in Gitlab 14.0" announcement_milestone: "14.7" # The milestone when this feature was deprecated. announcement_date: "2022-01-22" # The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is being removed. diff --git a/data/removals/15_0/15_0-remove-pipelines-from-version-field.yml b/data/removals/15_0/15_0-remove-pipelines-from-version-field.yml index df0c4c74e2e..e826943f7f1 100644 --- a/data/removals/15_0/15_0-remove-pipelines-from-version-field.yml +++ b/data/removals/15_0/15_0-remove-pipelines-from-version-field.yml @@ -1,4 +1,4 @@ -- name: "Pipelines field from the version field" # The name of the feature to be deprecated +- title: "Pipelines field from the version field" # 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 diff --git a/data/removals/15_0/removal-manage-premium-required-pipelines.yml b/data/removals/15_0/removal-manage-premium-required-pipelines.yml index 1e91fe1d3fc..4a9105bf63d 100644 --- a/data/removals/15_0/removal-manage-premium-required-pipelines.yml +++ b/data/removals/15_0/removal-manage-premium-required-pipelines.yml @@ -1,4 +1,4 @@ -- name: "Required pipeline configurations in Premium tier" +- title: "Required pipeline configurations in Premium tier" announcement_milestone: "14.8" announcement_date: "2021-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/removal_manage_optional_pat_expiration.yml b/data/removals/15_0/removal_manage_optional_pat_expiration.yml index 21c5b99d1a8..e1e6a125186 100644 --- a/data/removals/15_0/removal_manage_optional_pat_expiration.yml +++ b/data/removals/15_0/removal_manage_optional_pat_expiration.yml @@ -1,4 +1,4 @@ -- name: "Optional enforcement of personal access token expiration" +- title: "Optional enforcement of personal access token expiration" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/removal_manage_repository_push_audit_event.yml b/data/removals/15_0/removal_manage_repository_push_audit_event.yml index 474a5c41a95..c1c47823325 100644 --- a/data/removals/15_0/removal_manage_repository_push_audit_event.yml +++ b/data/removals/15_0/removal_manage_repository_push_audit_event.yml @@ -1,4 +1,4 @@ -- name: "Audit events for repository push events" +- title: "Audit events for repository push events" announcement_milestone: "14.3" announcement_date: "2021-09-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/removal_manage_ssh_expiration.yml b/data/removals/15_0/removal_manage_ssh_expiration.yml index accd1d49f6f..889d79c8a29 100644 --- a/data/removals/15_0/removal_manage_ssh_expiration.yml +++ b/data/removals/15_0/removal_manage_ssh_expiration.yml @@ -1,4 +1,4 @@ -- name: "Optional enforcement of SSH expiration" +- title: "Optional enforcement of SSH expiration" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_0/removal_manage_status_check_passed_status.yml b/data/removals/15_0/removal_manage_status_check_passed_status.yml index 598cba369cb..b5e63812d7c 100644 --- a/data/removals/15_0/removal_manage_status_check_passed_status.yml +++ b/data/removals/15_0/removal_manage_status_check_passed_status.yml @@ -1,4 +1,4 @@ -- name: "External status check API breaking changes" +- title: "External status check API breaking changes" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.0" diff --git a/data/removals/15_2/removal-outdated-browser-support.yml b/data/removals/15_2/removal-outdated-browser-support.yml index 84b2fa32020..bbe6892a5f5 100644 --- a/data/removals/15_2/removal-outdated-browser-support.yml +++ b/data/removals/15_2/removal-outdated-browser-support.yml @@ -1,4 +1,4 @@ -- name: "Support for older browsers" +- title: "Support for older browsers" removal_date: July 22, 2022 removal_milestone: "15.2" reporter: leipert diff --git a/data/removals/15_3/15-3-vulnerability-report-state-sort.yml b/data/removals/15_3/15-3-vulnerability-report-state-sort.yml index 3ba5b451718..a9c84827b7c 100644 --- a/data/removals/15_3/15-3-vulnerability-report-state-sort.yml +++ b/data/removals/15_3/15-3-vulnerability-report-state-sort.yml @@ -1,7 +1,7 @@ # # REQUIRED FIELDS # -- name: "Vulnerability Report sort by State" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. +- title: "Vulnerability Report sort by State" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. announcement_milestone: "15.0" # (required) The milestone when this feature was deprecated. announcement_date: "2022-05-22" # (required) The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "15.3" # (required) The milestone when this feature is being removed. diff --git a/data/removals/15_3/15-3-vulnerability-report-tool-sort.yml b/data/removals/15_3/15-3-vulnerability-report-tool-sort.yml index 9aba5ca5ee7..6743a43d4b3 100644 --- a/data/removals/15_3/15-3-vulnerability-report-tool-sort.yml +++ b/data/removals/15_3/15-3-vulnerability-report-tool-sort.yml @@ -1,7 +1,7 @@ # # REQUIRED FIELDS # -- name: "Vulnerability Report sort by Tool" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. +- title: "Vulnerability Report sort by Tool" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. announcement_milestone: "15.1" # (required) The milestone when this feature was deprecated. announcement_date: "2022-06-22" # (required) The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "15.3" # (required) The milestone when this feature is being removed. diff --git a/data/removals/15_3/removal_debian9.yml b/data/removals/15_3/removal_debian9.yml index 5438922173f..eca198d6b18 100644 --- a/data/removals/15_3/removal_debian9.yml +++ b/data/removals/15_3/removal_debian9.yml @@ -1,4 +1,4 @@ -- name: "Support for Debian 9" +- title: "Support for Debian 9" removal_date: Aug 22, 2022 # day the removal was released removal_milestone: "15.3" reporter: dorrino # GitLab username of the person reporting the removal diff --git a/data/removals/15_4/15-4-sast-analyzer-consolidation.yml b/data/removals/15_4/15-4-sast-analyzer-consolidation.yml index 825fb2b4bfc..61358d3653b 100644 --- a/data/removals/15_4/15-4-sast-analyzer-consolidation.yml +++ b/data/removals/15_4/15-4-sast-analyzer-consolidation.yml @@ -1,4 +1,4 @@ -- name: "SAST analyzer consolidation and CI/CD template changes" +- title: "SAST analyzer consolidation and CI/CD template changes" announcement_milestone: "14.8" announcement_date: "2022-02-22" removal_milestone: "15.4" diff --git a/data/removals/16_0/source_code-approvals-endpoint.yml b/data/removals/16_0/source_code-approvals-endpoint.yml index e754c1cfebf..cd3d87dc960 100644 --- a/data/removals/16_0/source_code-approvals-endpoint.yml +++ b/data/removals/16_0/source_code-approvals-endpoint.yml @@ -1,4 +1,4 @@ -- name: "Changing merge request approvals with the `/approvals` API endpoint" +- title: "Changing merge request approvals with the `/approvals` API endpoint" announcement_milestone: "12.3" announcement_date: "2019-09-22" removal_milestone: "16.0" diff --git a/data/removals/templates/_removal_template.md.erb b/data/removals/templates/_removal_template.md.erb index 322b5408442..89e25c76e04 100644 --- a/data/removals/templates/_removal_template.md.erb +++ b/data/removals/templates/_removal_template.md.erb @@ -37,7 +37,7 @@ For removal reviewers (Technical Writers only): <%- milestones.each do |milestone| %> ## Removed in <%= milestone %> <%- entries.select{|entry| entry["removal_milestone"] == milestone}.each do |removal| %> -### <%= removal["name"]%> +### <%= removal["title"]%> <% if removal["breaking_change"] -%> WARNING: diff --git a/data/removals/templates/example.yml b/data/removals/templates/example.yml index 8d7d694be26..e7c0268c182 100644 --- a/data/removals/templates/example.yml +++ b/data/removals/templates/example.yml @@ -12,7 +12,7 @@ # # REQUIRED FIELDS # -- name: "Feature name" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. +- title: "X is removed. Do Y instead." # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. announcement_milestone: "XX.YY" # (required) The milestone when this feature was deprecated. announcement_date: "YYYY-MM-DD" # (required) The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "XX.YY" # (required) The milestone when this feature is being removed. @@ -26,6 +26,16 @@ This area supports markdown. Delete this entire comment and replace it with your markdown content. + Removals must be actionable. + + Use terms such as "removed in favor of" or "use X instead." If no replacement is available, the action would be, "Discontinue use of foo immediately." + + For example: + + - The `confidential` field for a `Note` is removed. Use `internal` instead. + - The `merge_status` field in the merge request API has been removed in favor of `detailed_merge_status`. + - The `notable` endpoint has been removed. Discontinue use of `notable` immediately. + When ready, assign to your tech writer for review. When ready, they will run `bin/rake gitlab:docs:compile_removals` to update the removals doc, then merge. END OF BODY COMMENT --> diff --git a/doc/administration/gitaly/praefect.md b/doc/administration/gitaly/praefect.md index 19ce24a6064..fd490e3b627 100644 --- a/doc/administration/gitaly/praefect.md +++ b/doc/administration/gitaly/praefect.md @@ -46,15 +46,15 @@ default value. The default value depends on the GitLab version. Network latency for Gitaly Cluster should ideally be measurable in single-digit milliseconds. Latency is particularly important for: -- Gitaly node health checks. Nodes must be able to respond within 1 second. +- Gitaly node health checks. Nodes must be able to respond 1 second or faster. - Reference transactions that enforce [strong consistency](index.md#strong-consistency). Lower latencies mean Gitaly nodes can agree on changes faster. Achieving acceptable latency between Gitaly nodes: - On physical networks generally means high bandwidth, single location connections. -- On the cloud generally means within the same region, including allowing cross availability zone replication. These links - are designed for this type of synchronization. Latency of less than 2ms should be sufficient for Gitaly Cluster. +- On the cloud generally means in the same region, including allowing cross availability zone replication. These links + are designed for this type of synchronization. Latency of less than 2 ms should be sufficient for Gitaly Cluster. If you can't provide low network latencies for replication (for example, between distant locations), consider Geo. For more information, see [Comparison to Geo](index.md#comparison-to-geo). @@ -85,7 +85,7 @@ The requirements are relatively low because the database contains only metadata - Where repositories are located. - Some queued work. -It depends on the number of repositories, but a useful minimum is 5-10 GB, similar to the main +It depends on the number of repositories, but a good minimum is 5-10 GB, similar to the main GitLab application database. ## Setup Instructions @@ -106,7 +106,7 @@ If you [installed](https://about.gitlab.com/install/) GitLab using the Omnibus G Before beginning, you should already have a working GitLab instance. [Learn how to install GitLab](https://about.gitlab.com/install/). -Provision a PostgreSQL server. We recommend using the PostgreSQL that is shipped +Provision a PostgreSQL server. You should use the PostgreSQL that is shipped with Omnibus GitLab and use it to configure the PostgreSQL database. You can use an external PostgreSQL server (version 11 or newer) but you must set it up [manually](#manual-database-setup). diff --git a/doc/administration/gitaly/reference.md b/doc/administration/gitaly/reference.md index 8f7dc688e56..8c05e4ad611 100644 --- a/doc/administration/gitaly/reference.md +++ b/doc/administration/gitaly/reference.md @@ -57,7 +57,7 @@ an empty string. It is possible to temporarily disable authentication with the `transitioning` setting. This allows you to monitor if all clients are authenticating correctly without causing a service outage for clients -that are not configured correctly yet: +that are still to be configured correctly: ```toml [auth] @@ -169,7 +169,7 @@ Gitaly restarts its `gitaly-ruby` helpers when their memory exceeds the | Name | Type | Required | Description | | ---- | ---- | -------- | ----------- | | `dir` | string | yes | Path to where `gitaly-ruby` is installed (needed to boot the process).| -| `max_rss` | integer | no | Resident set size limit that triggers a `gitaly-ruby` restart, in bytes. Default is `200000000` (200MB). | +| `max_rss` | integer | no | Resident set size limit that triggers a `gitaly-ruby` restart, in bytes. Default is `200000000` (200 MB). | | `graceful_restart_timeout` | string | no | Grace period before a `gitaly-ruby` process is forcibly terminated after exceeding `max_rss`. Default is `10m` (10 minutes).| | `restart_delay` | string | no |Time that `gitaly-ruby` memory must remain high before a restart. Default is `5m` (5 minutes).| | `num_workers` | integer | no |Number of `gitaly-ruby` worker processes. Try increasing this number in case of `ResourceExhausted` errors. Default is `2`, minimum is `2`.| diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md index 546c4667220..a3b9df81a25 100644 --- a/doc/administration/instance_limits.md +++ b/doc/administration/instance_limits.md @@ -818,9 +818,9 @@ This limit is [enabled on GitLab.com](../user/gitlab_com/index.md#gitlab-cicd). You can set a limit on the maximum size of a dotenv artifact. This limit is checked every time a dotenv file is exported as an artifact. -Set the limit to `0` to disable it. Defaults to 5KB. +Set the limit to `0` to disable it. Defaults to 5 KB. -To set this limit to 5KB on a self-managed installation, run the following in the +To set this limit to 5 KB on a self-managed installation, run the following in the [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session): ```ruby diff --git a/doc/administration/job_logs.md b/doc/administration/job_logs.md index 5aa0e8f3948..9b25c70716b 100644 --- a/doc/administration/job_logs.md +++ b/doc/administration/job_logs.md @@ -158,7 +158,7 @@ To eliminate both file system requirements: The data flow is the same as described in the [data flow section](#data-flow) with one change: _the stored path of the first two phases is different_. This incremental log architecture stores chunks of logs in Redis and a persistent store (object storage or database) instead of -file storage. Redis is used as first-class storage, and it stores up-to 128KB +file storage. Redis is used as first-class storage, and it stores up-to 128 KB of data. After the full chunk is sent, it is flushed to a persistent store, either object storage (temporary directory) or database. After a while, the data in Redis and a persistent store is archived to [object storage](#uploading-logs-to-object-storage). @@ -169,7 +169,7 @@ Here is the detailed data flow: 1. The runner picks a job from GitLab 1. The runner sends a piece of log to GitLab 1. GitLab appends the data to Redis -1. After the data in Redis reaches 128KB, the data is flushed to a persistent store (object storage or the database). +1. After the data in Redis reaches 128 KB, the data is flushed to a persistent store (object storage or the database). 1. The above steps are repeated until the job is finished. 1. After the job is finished, GitLab schedules a Sidekiq worker to archive the log. 1. The Sidekiq worker archives the log to object storage and cleans up the log diff --git a/doc/administration/lfs/index.md b/doc/administration/lfs/index.md index 31ca71598c7..80ee9278d09 100644 --- a/doc/administration/lfs/index.md +++ b/doc/administration/lfs/index.md @@ -291,7 +291,7 @@ sudo gitlab-rails console Set up timeouts: - These settings are only in effect for the same session. For example, they are not effective for Sidekiq workers. -- 20 minutes (1200 sec) is enough to upload 30GB LFS files: +- 20 minutes (1200 sec) is enough to upload 30 GB LFS files: ```ruby ::Google::Apis::ClientOptions.default.open_timeout_sec = 1200 @@ -343,7 +343,7 @@ An error occurred while loading the file. Please try again later. This occurs due to Cross-Origin Resource Sharing (CORS) restrictions: the browser attempts to load the PDF from object storage, but the object -storage provider rejects the request since the GitLab domain differs +storage provider rejects the request because the GitLab domain differs from the object storage domain. To fix this issue, configure your object storage provider's CORS diff --git a/doc/administration/operations/filesystem_benchmarking.md b/doc/administration/operations/filesystem_benchmarking.md index ec2975baf52..cd4ab1a9cf8 100644 --- a/doc/administration/operations/filesystem_benchmarking.md +++ b/doc/administration/operations/filesystem_benchmarking.md @@ -19,7 +19,7 @@ I/O. The information on this page can be used for either scenario. ### Benchmarking with `fio` -We recommend using +You should use [Fio](https://fio.readthedocs.io/en/latest/fio_doc.html) to test I/O performance. This test should be run both on the NFS server and on the application nodes that talk to the NFS server. @@ -35,8 +35,8 @@ Then run the following: fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --bs=4k --iodepth=64 --readwrite=randrw --rwmixread=75 --size=4G --filename=/path/to/git-data/testfile ``` -This creates a 4GB file in `/path/to/git-data/testfile`. It performs -4KB reads and writes using a 75%/25% split in the file, with 64 +This creates a 4 GB file in `/path/to/git-data/testfile`. It performs +4 KB reads and writes using a 75%/25% split in the file, with 64 operations running at a time. Be sure to delete the file after the test completes. diff --git a/doc/administration/operations/puma.md b/doc/administration/operations/puma.md index eb326c06e6a..af595cdf297 100644 --- a/doc/administration/operations/puma.md +++ b/doc/administration/operations/puma.md @@ -66,9 +66,9 @@ From this output: - The formula that calculates the maximum memory value results in workers being killed before they reach the `per_worker_max_memory_mb` value. -- In GitLab 13.4 and earlier, the default values for the formula were 550MB for the primary - and 850MB for each worker. -- In GitLab 13.5 and later, the values are primary: 800MB, worker: 1024MB. +- In GitLab 13.4 and earlier, the default values for the formula were 550 MB for the primary + and 850 MB for each worker. +- In GitLab 13.5 and later, the values are primary: 800 MB, worker: 1024 MB. - The threshold for workers to be killed is set at 98% of the limit: ```plaintext @@ -110,11 +110,11 @@ To change the worker timeout to 600 seconds: WARNING: This is an experimental [Alpha feature](../../policy/alpha-beta-support.md#alpha-features) and subject to change without notice. The feature -is not ready for production use. If you want to use this feature, we recommend testing +is not ready for production use. If you want to use this feature, you should test outside of production first. See the [known issues](#puma-single-mode-known-issues) for additional details. -In a memory-constrained environment with less than 4GB of RAM available, consider disabling Puma +In a memory-constrained environment with less than 4 GB of RAM available, consider disabling Puma [clustered mode](https://github.com/puma/puma#clustered-mode). Set the number of `workers` to `0` to reduce memory usage by hundreds of MB: diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md index 2623f2afd8d..d0277d9936d 100644 --- a/doc/administration/packages/container_registry.md +++ b/doc/administration/packages/container_registry.md @@ -1348,7 +1348,7 @@ level=error msg="response completed with error" err.code=unknown err.detail="une ``` To resolve the error specify a `chunksize` value in the Registry configuration. -Start with a value between `25000000` (25MB) and `50000000` (50MB). +Start with a value between `25000000` (25 MB) and `50000000` (50 MB). **For Omnibus installations** diff --git a/doc/api/alert_management_alerts.md b/doc/api/alert_management_alerts.md index bf3d6287341..702d453e140 100644 --- a/doc/api/alert_management_alerts.md +++ b/doc/api/alert_management_alerts.md @@ -33,7 +33,7 @@ Example response: "created_at": "2020-11-12T20:07:58.156Z", "filename": "sample_2054", "file_path": "/uploads/-/system/alert_metric_image/file/17/sample_2054.png", - "url": "example.com/metric", + "url": "https://example.com/metric", "url_text": "An example metric" } ``` @@ -62,7 +62,7 @@ Example response: "created_at": "2020-11-12T20:07:58.156Z", "filename": "sample_2054", "file_path": "/uploads/-/system/alert_metric_image/file/17/sample_2054.png", - "url": "example.com/metric", + "url": "https://example.com/metric", "url_text": "An example metric" }, { @@ -70,7 +70,7 @@ Example response: "created_at": "2020-11-12T20:14:26.441Z", "filename": "sample_2054", "file_path": "/uploads/-/system/alert_metric_image/file/18/sample_2054.png", - "url": "example.com/metric", + "url": "https://example.com/metric", "url_text": "An example metric" } ] @@ -102,8 +102,8 @@ Example response: "created_at": "2020-11-13T00:06:18.084Z", "filename": "file.png", "file_path": "/uploads/-/system/alert_metric_image/file/23/file.png", - "url": "http://example.com", - "url_text": "Example website" + "url": "https://example.com/metric", + "url_text": "An example metric" } ``` diff --git a/doc/api/groups.md b/doc/api/groups.md index cba54648705..94febd0ac0d 100644 --- a/doc/api/groups.md +++ b/doc/api/groups.md @@ -30,7 +30,7 @@ Parameters: | `statistics` | boolean | no | Include group statistics (administrators only) | | `with_custom_attributes` | boolean | no | Include [custom attributes](custom_attributes.md) in response (administrators only) | | `owned` | boolean | no | Limit to groups explicitly owned by the current user | -| `min_access_level` | integer | no | Limit to groups where current user has at least this [access level](members.md#valid-access-levels) | +| `min_access_level` | integer | no | Limit to groups where current user has at least this [role (`access_level`)](members.md#roles) | | `top_level_only` | boolean | no | Limit to top level groups, excluding all subgroups | ```plaintext @@ -148,7 +148,7 @@ Parameters: | `statistics` | boolean | no | Include group statistics (administrators only) | | `with_custom_attributes` | boolean | no | Include [custom attributes](custom_attributes.md) in response (administrators only) | | `owned` | boolean | no | Limit to groups explicitly owned by the current user | -| `min_access_level` | integer | no | Limit to groups where current user has at least this [access level](members.md#valid-access-levels) | +| `min_access_level` | integer | no | Limit to groups where current user has at least this [role (`access_level`)](members.md#roles) | ```plaintext GET /groups/:id/subgroups @@ -206,7 +206,7 @@ Parameters: | `statistics` | boolean | no | Include group statistics (administrators only) | | `with_custom_attributes` | boolean | no | Include [custom attributes](custom_attributes.md) in response (administrators only) | | `owned` | boolean | no | Limit to groups explicitly owned by the current user | -| `min_access_level` | integer | no | Limit to groups where current user has at least this [access level](members.md#valid-access-levels) | +| `min_access_level` | integer | no | Limit to groups where current user has at least this [role (`access_level`)](members.md#roles) | ```plaintext GET /groups/:id/descendant_groups @@ -294,7 +294,7 @@ Parameters: | `with_merge_requests_enabled` | boolean | no | Limit by projects with merge requests feature enabled. Default is `false` | | `with_shared` | boolean | no | Include projects shared to this group. Default is `true` | | `include_subgroups` | boolean | no | Include projects in subgroups of this group. Default is `false` | -| `min_access_level` | integer | no | Limit to projects where current user has at least this [access level](members.md#valid-access-levels) | +| `min_access_level` | integer | no | Limit to projects where current user has at least this [role (`access_level`)](members.md#roles) | | `with_custom_attributes` | boolean | no | Include [custom attributes](custom_attributes.md) in response (administrators only) | | `with_security_reports` **(ULTIMATE)** | boolean | no | Return only projects that have security reports artifacts present in any of their builds. This means "projects with security reports enabled". Default is `false` | @@ -374,7 +374,7 @@ Parameters: | `starred` | boolean | no | Limit by projects starred by the current user | | `with_issues_enabled` | boolean | no | Limit by projects with issues feature enabled. Default is `false` | | `with_merge_requests_enabled` | boolean | no | Limit by projects with merge requests feature enabled. Default is `false` | -| `min_access_level` | integer | no | Limit to projects where current user has at least this [access level](members.md#valid-access-levels) | +| `min_access_level` | integer | no | Limit to projects where current user has at least this [role (`access_level`)](members.md#roles) | | `with_custom_attributes` | boolean | no | Include [custom attributes](custom_attributes.md) in response (administrators only) | Example response: @@ -1444,7 +1444,7 @@ POST /groups/:id/ldap_group_links | `id` | integer/string | yes | The ID or [URL-encoded path of the group](index.md#namespaced-path-encoding) | | `cn` | string | no | The CN of an LDAP group | | `filter` | string | no | The LDAP filter for the group | -| `group_access` | integer | yes | [Access level](members.md#valid-access-levels) for members of the LDAP group | +| `group_access` | integer | yes | [Role (`access_level`)](members.md#roles) for members of the LDAP group | | `provider` | string | yes | LDAP provider for the LDAP group link | NOTE: @@ -1519,7 +1519,7 @@ If successful, returns [`200`](index.md#status-codes) and the following response | Attribute | Type | Description | |:-------------------|:--------|:-----------------------------------------------------------------------------| | `[].name` | string | Name of the SAML group | -| `[].access_level` | integer | [Access level](members.md#valid-access-levels) for members of the SAML group. The attribute had a string type from GitLab 15.3.0 to GitLab 15.3.3 | +| `[].access_level` | integer | [Role (`access_level`)](members.md#roles) for members of the SAML group. The attribute had a string type from GitLab 15.3.0 to GitLab 15.3.3 | Example request: @@ -1562,7 +1562,7 @@ If successful, returns [`200`](index.md#status-codes) and the following response | Attribute | Type | Description | |:---------------|:--------|:-----------------------------------------------------------------------------| | `name` | string | Name of the SAML group | -| `access_level` | integer | [Access level](members.md#valid-access-levels) for members of the SAML group. The attribute had a string type from GitLab 15.3.0 to GitLab 15.3.3 | +| `access_level` | integer | [Role (`access_level`)](members.md#roles) for members of the SAML group. The attribute had a string type from GitLab 15.3.0 to GitLab 15.3.3 | Example request: @@ -1593,14 +1593,14 @@ Supported attributes: |:-------------------|:---------------|:---------|:-----------------------------------------------------------------------------| | `id` | integer or string | yes | ID or [URL-encoded path of the group](index.md#namespaced-path-encoding) | | `saml_group_name` | string | yes | Name of a SAML group | -| `access_level` | integer | yes | [Access level](members.md#valid-access-levels) for members of the SAML group | +| `access_level` | integer | yes | [Role (`access_level`)](members.md#roles) for members of the SAML group | If successful, returns [`201`](index.md#status-codes) and the following response attributes: | Attribute | Type | Description | |:---------------|:--------|:-----------------------------------------------------------------------------| | `name` | string | Name of the SAML group | -| `access_level` | integer | [Access level](members.md#valid-access-levels) for members of the for members of the SAML group. The attribute had a string type from GitLab 15.3.0 to GitLab 15.3.3 | +| `access_level` | integer | [Role (`access_level`)](members.md#roles) for members of the for members of the SAML group. The attribute had a string type from GitLab 15.3.0 to GitLab 15.3.3 | Example request: @@ -1682,7 +1682,7 @@ POST /groups/:id/share | --------- | -------------- | -------- | ----------- | | `id` | integer/string | yes | The ID or [URL-encoded path of the group](index.md#namespaced-path-encoding) | | `group_id` | integer | yes | The ID of the group to share with | -| `group_access` | integer | yes | The [access level](members.md#valid-access-levels) to grant the group | +| `group_access` | integer | yes | The [role (`access_level`)](members.md#roles) to grant the group | | `expires_at` | string | no | Share expiration date in ISO 8601 format: 2016-09-26 | ### Delete link sharing group with another group diff --git a/doc/api/members.md b/doc/api/members.md index 66729abcad8..7adf2f1a40f 100644 --- a/doc/api/members.md +++ b/doc/api/members.md @@ -8,9 +8,10 @@ info: To determine the technical writer assigned to the Stage/Group associated w > `created_by` field [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/28789) in GitLab 14.10. -## Valid access levels +## Roles -The access levels are defined in the `Gitlab::Access` module. Currently, these levels are recognized: +The [role](../user/permissions.md) assigned to a user or group is defined +in the `Gitlab::Access` module as `access_level`. - No access (`0`) - Minimal access (`5`) ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/220203) in GitLab 13.5.) diff --git a/doc/api/projects.md b/doc/api/projects.md index 638af168f22..82a3388053f 100644 --- a/doc/api/projects.md +++ b/doc/api/projects.md @@ -54,7 +54,7 @@ GET /projects | `last_activity_after` | datetime | **{dotted-circle}** No | Limit results to projects with last_activity after specified time. Format: ISO 8601 (`YYYY-MM-DDTHH:MM:SSZ`) | | `last_activity_before` | datetime | **{dotted-circle}** No | Limit results to projects with last_activity before specified time. Format: ISO 8601 (`YYYY-MM-DDTHH:MM:SSZ`) | | `membership` | boolean | **{dotted-circle}** No | Limit by projects that the current user is a member of. | -| `min_access_level` | integer | **{dotted-circle}** No | Limit by current user minimal [access level](members.md#valid-access-levels). | +| `min_access_level` | integer | **{dotted-circle}** No | Limit by current user minimal [role (`access_level`)](members.md#roles). | | `order_by` | string | **{dotted-circle}** No | Return projects ordered by `id`, `name`, `path`, `created_at`, `updated_at`, `last_activity_at`, or `similarity` fields. `repository_size`, `storage_size`, `packages_size` or `wiki_size` fields are only allowed for administrators. `similarity` ([introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/332890) in GitLab 14.1) is only available when searching and is limited to projects that the current user is a member of. Default is `created_at`. | | `owned` | boolean | **{dotted-circle}** No | Limit by projects explicitly owned by the current user. | | `repository_checksum_failed` **(PREMIUM)** | boolean | **{dotted-circle}** No | Limit projects where the repository checksum calculation has failed. | @@ -333,7 +333,7 @@ GET /users/:user_id/projects | `id_after` | integer | **{dotted-circle}** No | Limit results to projects with IDs greater than the specified ID. | | `id_before` | integer | **{dotted-circle}** No | Limit results to projects with IDs less than the specified ID. | | `membership` | boolean | **{dotted-circle}** No | Limit by projects that the current user is a member of. | -| `min_access_level` | integer | **{dotted-circle}** No | Limit by current user minimal [access level](members.md#valid-access-levels). | +| `min_access_level` | integer | **{dotted-circle}** No | Limit by current user minimal [role (`access_level`)](members.md#roles). | | `order_by` | string | **{dotted-circle}** No | Return projects ordered by `id`, `name`, `path`, `created_at`, `updated_at`, or `last_activity_at` fields. Default is `created_at`. | | `owned` | boolean | **{dotted-circle}** No | Limit by projects explicitly owned by the current user. | | `search` | string | **{dotted-circle}** No | Return list of projects matching the search criteria. | @@ -590,7 +590,7 @@ GET /users/:user_id/starred_projects | `user_id` | string | **{check-circle}** Yes | The ID or username of the user. | | `archived` | boolean | **{dotted-circle}** No | Limit by archived status. | | `membership` | boolean | **{dotted-circle}** No | Limit by projects that the current user is a member of. | -| `min_access_level` | integer | **{dotted-circle}** No | Limit by current user minimal [access level](members.md#valid-access-levels). | +| `min_access_level` | integer | **{dotted-circle}** No | Limit by current user minimal [role (`access_level`)](members.md#roles). | | `order_by` | string | **{dotted-circle}** No | Return projects ordered by `id`, `name`, `path`, `created_at`, `updated_at`, or `last_activity_at` fields. Default is `created_at`. | | `owned` | boolean | **{dotted-circle}** No | Limit by projects explicitly owned by the current user. | | `search` | string | **{dotted-circle}** No | Return list of projects matching the search criteria. | @@ -1150,7 +1150,7 @@ GET /projects/:id/groups |-----------------------------|-------------------|------------------------|-------------| | `id` | integer or string | **{check-circle}** Yes | The ID or [URL-encoded path of the project](index.md#namespaced-path-encoding). | | `search` | string | **{dotted-circle}** No | Search for specific groups. | -| `shared_min_access_level` | integer | **{dotted-circle}** No | Limit to shared groups with at least this [access level](members.md#valid-access-levels). | +| `shared_min_access_level` | integer | **{dotted-circle}** No | Limit to shared groups with at least this [role (`access_level`)](members.md#roles). | | `shared_visible_only` | boolean | **{dotted-circle}** No | Limit to shared groups user has access to. | | `skip_groups` | array of integers | **{dotted-circle}** No | Skip the group IDs passed. | | `with_shared` | boolean | **{dotted-circle}** No | Include projects shared with this group. Default is `false`. | @@ -1496,7 +1496,7 @@ GET /projects/:id/forks | `id` | integer or string | **{check-circle}** Yes | The ID or [URL-encoded path of the project](index.md#namespaced-path-encoding). | | `archived` | boolean | **{dotted-circle}** No | Limit by archived status. | | `membership` | boolean | **{dotted-circle}** No | Limit by projects that the current user is a member of. | -| `min_access_level` | integer | **{dotted-circle}** No | Limit by current user minimal [access level](members.md#valid-access-levels). | +| `min_access_level` | integer | **{dotted-circle}** No | Limit by current user minimal [role (`access_level`)](members.md#roles). | | `order_by` | string | **{dotted-circle}** No | Return projects ordered by `id`, `name`, `path`, `created_at`, `updated_at`, or `last_activity_at` fields. Default is `created_at`. | | `owned` | boolean | **{dotted-circle}** No | Limit by projects explicitly owned by the current user. | | `search` | string | **{dotted-circle}** No | Return list of projects matching the search criteria. | @@ -2310,7 +2310,7 @@ POST /projects/:id/share | Attribute | Type | Required | Description | |----------------|----------------|------------------------|-------------| -| `group_access` | integer | **{check-circle}** Yes | The [access level](members.md#valid-access-levels) to grant the group. | +| `group_access` | integer | **{check-circle}** Yes | The [role (`access_level`)](members.md#roles) to grant the group. | | `group_id` | integer | **{check-circle}** Yes | The ID of the group to share with. | | `id` | integer or string | **{check-circle}** Yes | The ID or [URL-encoded path of the project](index.md#namespaced-path-encoding). | | `expires_at` | string | **{dotted-circle}** No | Share expiration date in ISO 8601 format: 2016-09-26 | diff --git a/doc/api/saml.md b/doc/api/saml.md index 810ed382d49..4b0e57111cc 100644 --- a/doc/api/saml.md +++ b/doc/api/saml.md @@ -35,9 +35,7 @@ response attributes: Example request: ```shell -curl --location --request GET "https://gdk.test:3443/api/v4/groups/33/saml/identities" \ ---header "<PRIVATE-TOKEN>" \ ---form "extern_uid=<ID_TO_BE_UPDATED>" \ +curl --location --request GET "https://gitlab.example.com/api/v4/groups/33/saml/identities" --header "<PRIVATE-TOKEN>" ``` Example response: @@ -53,7 +51,7 @@ Example response: ## Update `extern_uid` field for a SAML identity -Update `extern_uid` field for a SAML identity. Field that can be updated are: +Update `extern_uid` field for a SAML identity: | SAML IdP attribute | GitLab field | | ------------------ | ------------ | @@ -72,7 +70,7 @@ Parameters: Example request: ```shell -curl --location --request PATCH "https://gdk.test:3443/api/v4/groups/33/saml/sydney_jones" \ +curl --location --request PATCH "https://gitlab.example.com/api/v4/groups/33/saml/sydney_jones" \ --header "<PRIVATE TOKEN>" \ --form "extern_uid=sydney_jones_new" \ ``` diff --git a/doc/api/scim.md b/doc/api/scim.md index 53897cadf90..006af7a6eff 100644 --- a/doc/api/scim.md +++ b/doc/api/scim.md @@ -50,11 +50,10 @@ Example request: ```shell curl --location --request GET "https://gitlab.example.com/api/v4/groups/33/scim/identities" \ ---header "PRIVATE-TOKEN: <PRIVATE-TOKEN>" \ ---form "extern_uid=<ID_TO_BE_UPDATED>" \ +--header "PRIVATE-TOKEN: <PRIVATE-TOKEN>" ``` -## Update extern_uid field for a SCIM identity +## Update `extern_uid` field for a SCIM identity > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/227841) in GitLab 15.5. @@ -79,5 +78,5 @@ Example request: ```shell curl --location --request PATCH "https://gitlab.example.com/api/v4/groups/33/scim/sydney_jones" \ --header "PRIVATE-TOKEN: <PRIVATE TOKEN>" \ ---form "extern_uid=sydney_jones_new" \ +--form "extern_uid=sydney_jones_new" ``` diff --git a/doc/architecture/blueprints/database/scalability/patterns/time_decay.md b/doc/architecture/blueprints/database/scalability/patterns/time_decay.md index 93f5dffd3f5..2b36a43a6db 100644 --- a/doc/architecture/blueprints/database/scalability/patterns/time_decay.md +++ b/doc/architecture/blueprints/database/scalability/patterns/time_decay.md @@ -154,7 +154,7 @@ factors: The perfect partitioning scheme keeps **all queries over a dataset almost always over a single partition**, with some cases going over two partitions and seldom over multiple partitions being an acceptable balance. We should also target for **partitions that are as small as possible**, below -5-10M records and/or 10GB each maximum. +5-10M records and/or 10 GB each maximum. Partitioning can be combined with other strategies to either prune (drop) old partitions, move them to cheaper storage inside the database or move them outside of the database (archive or use of other @@ -241,7 +241,7 @@ Related epic: [Partitioning: `web_hook_logs` table](https://gitlab.com/groups/gi The important characteristics of `web_hook_logs` are the following: 1. Size of the dataset: it is a really large table. At the moment we decided to - partition it (`2021-03-01`), it had roughly 527M records and a total size of roughly 1TB + partition it (`2021-03-01`), it had roughly 527M records and a total size of roughly 1 TB - Table: `web_hook_logs` - Rows: approximately 527M @@ -261,7 +261,7 @@ As a result, on March 2021 there were still not deleted records since July 2020 increasing in size by more than 2 million records per day instead of staying at a more or less stable size. -Finally, the rate of inserts has grown to more than 170GB of data per month by March 2021 and keeps +Finally, the rate of inserts has grown to more than 170 GB of data per month by March 2021 and keeps on growing, so the only viable solution to pruning old data was through partitioning. Our approach was to partition the table per month as it aligned with the 90 days retention policy. diff --git a/doc/architecture/blueprints/image_resizing/index.md b/doc/architecture/blueprints/image_resizing/index.md index 948378d8834..97bf520105a 100644 --- a/doc/architecture/blueprints/image_resizing/index.md +++ b/doc/architecture/blueprints/image_resizing/index.md @@ -14,7 +14,7 @@ Currently, we are showing all uploaded images 1:1, which is of course not ideal. ## MVC Avatar Resizing -When implementing a dynamic image resizing solution, images should be resized and optimized on the fly so that if we define new targeted sizes later we can add them dynamically. This would mean a huge improvement in performance as some of the measurements suggest that we can save up to 95% of our current load size. Our initial investigations indicate that we have uploaded approximately 1.65 million avatars totaling approximately 80GB in size and averaging approximately 48kb each. Early measurements indicate we can reduce the most common avatar dimensions to between 1-3kb in size, netting us a greater than 90% size reduction. For the MVC we don't consider application level caching and rely purely on HTTP based caches as implemented in CDNs and browsers, but might revisit this decision later on. To easily mitigate performance issues with avatar resizing, especially in the case of self managed, an operations feature flag is implemented to disable dynamic image resizing. +When implementing a dynamic image resizing solution, images should be resized and optimized on the fly so that if we define new targeted sizes later we can add them dynamically. This would mean a huge improvement in performance as some of the measurements suggest that we can save up to 95% of our current load size. Our initial investigations indicate that we have uploaded approximately 1.65 million avatars totaling approximately 80 GB in size and averaging approximately 48 KB each. Early measurements indicate we can reduce the most common avatar dimensions to between 1-3 KB in size, netting us a greater than 90% size reduction. For the MVC we don't consider application level caching and rely purely on HTTP based caches as implemented in CDNs and browsers, but might revisit this decision later on. To mitigate performance issues with avatar resizing, especially in the case of self managed, an operations feature flag is implemented to disable dynamic image resizing. ```mermaid sequenceDiagram @@ -38,10 +38,10 @@ sequenceDiagram Content image resizing is a more complex problem to tackle. There are no set size restrictions and there are additional features or requirements to consider. - Dynamic WebP support - the WebP format typically achieves an average of 30% more compression than JPEG without the loss of image quality. More details are in [this Google Comparative Study](https://developers.google.com/speed/webp/docs/c_study) -- Extract first image of GIF's so we can prevent from loading 10MB pixels +- Extract first image of GIF's so we can prevent from loading 10 MB pixels - Check Device Pixel Ratio to deliver nice images on High DPI screens - Progressive image loading, similar to what is described in [this article about how to build a progressive image loader](https://www.sitepoint.com/how-to-build-your-own-progressive-image-loader/) -- Resizing recommendations (size, clarity, and so on) +- Resizing recommendations (for example, size and clarity) - Storage The MVC Avatar resizing implementation is integrated into Workhorse. With the extra requirements for content image resizing, this may require further use of GraphicsMagik (GM) or a similar library and breaking it out of Workhorse. diff --git a/doc/architecture/blueprints/object_storage/index.md b/doc/architecture/blueprints/object_storage/index.md index 61dc37d7706..950a5f13c38 100644 --- a/doc/architecture/blueprints/object_storage/index.md +++ b/doc/architecture/blueprints/object_storage/index.md @@ -62,7 +62,7 @@ This has led to increased complexity across the board, from development that would normally be "free". - In many cases, we copy around object storage files needlessly (for example, [issue #285597](https://gitlab.com/gitlab-org/gitlab/-/issues/285597)). - Large files (LFS, packages, and so on) are slow to finalize or don't work + Large files (for example, LFS and packages) are slow to finalize or don't work at all as a result. ## Improvements over the current situation @@ -113,7 +113,7 @@ Because every group of features requires its own bucket, we don't have direct upload enabled everywhere. Contributing a new upload requires coding it in both Ruby on Rails and Go. -Implementing a new feature that does not yet have a dedicated bucket +Implementing a new feature that does not have a dedicated bucket requires the developer to also create a merge request in Omnibus and CNG, as well as coordinate with SREs to configure the new bucket for our own environments. @@ -138,7 +138,7 @@ access to new features without infrastructure chores. Our implementation is built on top of a 3rd-party framework where every object storage client is a 3rd-party library. Unfortunately some of them are unmaintained. -[We have customers who cannot push 5GB Git LFS objects](https://gitlab.com/gitlab-org/gitlab/-/issues/216442), +[We have customers who cannot push 5 GB Git LFS objects](https://gitlab.com/gitlab-org/gitlab/-/issues/216442), but with such a vital feature implemented in 3rd-party libraries we are slowed down in fixing it, and we also rely on external maintainers to merge and release fixes. diff --git a/doc/architecture/blueprints/pods/proposal-stateless-router-with-buffering-requests.md b/doc/architecture/blueprints/pods/proposal-stateless-router-with-buffering-requests.md index 21aa72273fe..d90df985da2 100644 --- a/doc/architecture/blueprints/pods/proposal-stateless-router-with-buffering-requests.md +++ b/doc/architecture/blueprints/pods/proposal-stateless-router-with-buffering-requests.md @@ -26,7 +26,7 @@ monolith. This architecture also supports regions by allowing for low traffic databases to be replicated across regions. Users are not directly exposed to the concept of Pods but instead they see -different data dependent on their currently chosen "organization". +different data dependent on their chosen "organization". [Organizations](index.md#organizations) will be a new model introduced to enforce isolation in the application and allow us to decide which request route to which pod, since an organization can only be on a single pod. @@ -615,9 +615,9 @@ Migrating data between pods will need to factor all data stores: ### Is it still possible to leak the existence of private groups via a timing attack? If you have router in EU, and you know that EU router by default redirects -to EU located Pods, you know their latency (lets assume 10ms). Now, if your +to EU located Pods, you know their latency (lets assume 10 ms). Now, if your request is bounced back and redirected to US which has different latency -(lets assume that roundtrip will be around 60ms) you can deduce that 404 was +(lets assume that roundtrip will be around 60 ms) you can deduce that 404 was returned by US Pod and know that your 404 is in fact 403. We may defer this until we actually implement a pod in a different region. Such timing attacks are already theoretically possible with the way we do permission checks today but the timing difference is probably too small to be able to detect. diff --git a/doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md b/doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md index e7520f3d6a8..c99b02a35e9 100644 --- a/doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md +++ b/doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md @@ -26,7 +26,7 @@ monolith. This architecture also supports regions by allowing for low traffic databases to be replicated across regions. Users are not directly exposed to the concept of Pods but instead they see -different data dependent on their currently chosen "organization". +different data dependent on their chosen "organization". [Organizations](index.md#organizations) will be a new model introduced to enforce isolation in the application and allow us to decide which request route to which pod, since an organization can only be on a single pod. @@ -639,9 +639,9 @@ Migrating data between pods will need to factor all data stores: ### Is it still possible to leak the existence of private groups via a timing attack? If you have router in EU, and you know that EU router by default redirects -to EU located Pods, you know their latency (lets assume 10ms). Now, if your +to EU located Pods, you know their latency (lets assume 10 ms). Now, if your request is bounced back and redirected to US which has different latency -(lets assume that roundtrip will be around 60ms) you can deduce that 404 was +(lets assume that roundtrip will be around 60 ms) you can deduce that 404 was returned by US Pod and know that your 404 is in fact 403. We may defer this until we actually implement a pod in a different region. Such timing attacks are already theoretically possible with the way we do permission checks today but the timing difference is probably too small to be able to detect. diff --git a/doc/architecture/blueprints/rate_limiting/index.md b/doc/architecture/blueprints/rate_limiting/index.md index ffe0712d69b..7ecd3bc1469 100644 --- a/doc/architecture/blueprints/rate_limiting/index.md +++ b/doc/architecture/blueprints/rate_limiting/index.md @@ -103,11 +103,11 @@ quota and by a policy. risks to performance, stability, and security. - _Example:_ API calls per second for a given IP address - _Example:_ `git clone` events per minute for a given user - - _Example:_ maximum artifact upload size of 1GB + - _Example:_ maximum artifact upload size of 1 GB - **Quota:** A global constraint in application usage that is aggregated across an entire namespace over the duration of their billing cycle. - _Example:_ 400 CI/CD minutes per namespace per month - - _Example:_ 10GB transfer per namespace per month + - _Example:_ 10 GB transfer per namespace per month - **Policy:** A representation of business logic that is decoupled from application code. Decoupled policy definitions allow logic to be shared across multiple services and/or "hot-loaded" at runtime without releasing a new version of the application. diff --git a/doc/ci/pipelines/cicd_minutes.md b/doc/ci/pipelines/cicd_minutes.md index 772a06980af..d9ad224ab95 100644 --- a/doc/ci/pipelines/cicd_minutes.md +++ b/doc/ci/pipelines/cicd_minutes.md @@ -126,7 +126,7 @@ These additional CI/CD minutes: - Are used only after the monthly quota included in your subscription runs out. - Are carried over to the next month, if any remain at the end of the month. -- Are valid for 12 months from date of purchase or until all minutes are consumed, whichever comes first. Expiry of minutes is not currently enforced. +- Are valid for 12 months from date of purchase or until all minutes are consumed, whichever comes first. Expiry of minutes is not enforced. For example, with a GitLab SaaS Premium license: @@ -137,7 +137,7 @@ For example, with a GitLab SaaS Premium license: If you use `13,000` minutes during the month, the next month your additional minutes become `2,000`. If you use `9,000` minutes during the month, your additional minutes remain the same. -If you bought additional CI/CD minutes while on a trial subscription those minutes will be available after the trial ends or you upgrade to a paid plan. +If you bought additional CI/CD minutes while on a trial subscription, those minutes are available after the trial ends or you upgrade to a paid plan. You can find pricing for additional CI/CD minutes on the [GitLab Pricing page](https://about.gitlab.com/pricing/). diff --git a/doc/ci/pipelines/downstream_pipelines.md b/doc/ci/pipelines/downstream_pipelines.md index c8fcd06da07..6c17c23552d 100644 --- a/doc/ci/pipelines/downstream_pipelines.md +++ b/doc/ci/pipelines/downstream_pipelines.md @@ -183,7 +183,7 @@ You can trigger a child pipeline from a YAML file generated in a job, instead of static file saved in your project. This technique can be very powerful for generating pipelines targeting content that changed or to build a matrix of targets and architectures. -The artifact containing the generated YAML file must not be [larger than 5MB](https://gitlab.com/gitlab-org/gitlab/-/issues/249140). +The artifact containing the generated YAML file must not be [larger than 5 MB](https://gitlab.com/gitlab-org/gitlab/-/issues/249140). <i class="fa fa-youtube-play youtube" aria-hidden="true"></i> For an overview, see [Create child pipelines using dynamically generated configurations](https://youtu.be/nMdfus2JWHM). diff --git a/doc/ci/runners/saas/linux_saas_runner.md b/doc/ci/runners/saas/linux_saas_runner.md index df7d5570953..a5750c47ea7 100644 --- a/doc/ci/runners/saas/linux_saas_runner.md +++ b/doc/ci/runners/saas/linux_saas_runner.md @@ -17,7 +17,7 @@ For Free, Premium, and Ultimate plan customers, jobs on these instances consume | | Small | Medium | Large | |-------------------|---------------------------|---------------------------|--------------------------| -| Specs | 1 vCPU, 3.75GB RAM | 2 vCPUs, 8GB RAM | 4 vCPUs, 16GB RAM | +| Specs | 1 vCPU, 3.75 GB RAM | 2 vCPUs, 8 GB RAM | 4 vCPUs, 16 GB RAM | | GitLab CI/CD tags | `saas-linux-small-amd64` | `saas-linux-medium-amd64` | `saas-linux-large-amd64` | | Subscription | Free, Premium, Ultimate | Free, Premium, Ultimate | Premium, Ultimate | @@ -78,7 +78,7 @@ Below are the settings for SaaS runners on Linux. - **Cache**: These runners share a [distributed cache](https://docs.gitlab.com/runner/configuration/autoscale.html#distributed-runners-caching) - that's stored in a Google Cloud Storage (GCS) bucket. Cache contents not updated within + that's stored in a Google Cloud Storage (GCS) bucket. Cache contents not updated in the last 14 days are automatically removed, based on the [object lifecycle management policy](https://cloud.google.com/storage/docs/lifecycle). @@ -88,8 +88,8 @@ Below are the settings for SaaS runners on Linux. and [#4070](https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/4070). NOTE: -The final disk space your jobs can use will be less than 25GB. Some disk space -allocated to the instance will be occupied by the operating system, the Docker image, +The final disk space your jobs can use is less than 25 GB. Some disk space +allocated to the instance is occupied by the operating system, the Docker image, and a copy of your cloned repository. ## Pre-clone script diff --git a/doc/ci/testing/unit_test_report_examples.md b/doc/ci/testing/unit_test_report_examples.md index 5d4cfa88d88..87426fc8496 100644 --- a/doc/ci/testing/unit_test_report_examples.md +++ b/doc/ci/testing/unit_test_report_examples.md @@ -42,7 +42,7 @@ Use the following job in `.gitlab-ci.yml`: golang: stage: test script: - - go get gotest.tools/gotestsum + - go install gotest.tools/gotestsum@latest - gotestsum --junitfile report.xml --format testname artifacts: when: always diff --git a/doc/update/index.md b/doc/update/index.md index 81911ef3d82..410cdadff70 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -501,7 +501,7 @@ and [Helm Chart deployments](https://docs.gitlab.com/charts/). They come with ap ### 15.3.3 - In GitLab 15.3.3, [SAML Group Links](../api/groups.md#saml-group-links) API `access_level` attribute type changed to `integer`. See -[valid access levels](../api/members.md#valid-access-levels) documentation. +[the API documentation](../api/members.md). ### 15.3.0 diff --git a/doc/user/permissions.md b/doc/user/permissions.md index 8e152a8c190..3c9f1544158 100644 --- a/doc/user/permissions.md +++ b/doc/user/permissions.md @@ -6,9 +6,11 @@ info: To determine the technical writer assigned to the Stage/Group associated w # Permissions and roles **(FREE)** -Users have different abilities depending on the role they have in a -particular group or project. If a user is both in a project's group and the -project itself, the highest role is used. +When you add a user to a project or group, you assign them a role. +The role determines which actions they can take in GitLab. + +If you add a user to both a project's group and the +project itself, the higher role is used. On [public and internal projects](../api/projects.md#project-visibility-level), the Guest role (not to be confused with [Guest user](#free-guest-users)) is not enforced. @@ -21,6 +23,19 @@ GitLab [administrators](../administration/index.md) receive all permissions. To add or import a user, you can follow the [project members documentation](project/members/index.md). +## Roles + +The available roles are: + +- Guest +- Reporter +- Developer +- Maintainer +- Owner + +A user assigned the Guest role has the least permissions, +and the Owner has the most. + ## Principles behind permissions See our [product handbook on permissions](https://about.gitlab.com/handbook/product/gitlab-the-product/#permissions-in-gitlab). @@ -33,8 +48,8 @@ usernames. A GitLab administrator can configure the GitLab instance to ## Project members permissions -- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/219299) in GitLab 14.8, personal namespace owners appear with Owner role in new projects in their namespace. Introduced [with a flag](../administration/feature_flags.md) named `personal_project_owner_with_owner_access`. Disabled by default. -- [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/351919) in GitLab 14.9. Feature flag `personal_project_owner_with_owner_access` [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/219299). +> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/219299) in GitLab 14.8, personal namespace owners appear with Owner role in new projects in their namespace. Introduced [with a flag](../administration/feature_flags.md) named `personal_project_owner_with_owner_access`. Disabled by default. +> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/351919) in GitLab 14.9. Feature flag `personal_project_owner_with_owner_access` [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/219299). A user's role determines what permissions they have on a project. The Owner role provides all permissions but is available only: @@ -161,7 +176,7 @@ The following table lists project permissions available for each role: | [Projects](project/index.md):<br>Edit comments (posted by any user) | | | | ✓ | ✓ | | [Projects](project/index.md):<br>Edit project badges | | | | ✓ | ✓ | | [Projects](project/index.md):<br>Edit project settings | | | | ✓ | ✓ | -| [Projects](project/index.md):<br>Export project | | | | ✓ | ✓ | +| [Projects](project/index.md):<br>[Export project](project/settings/import_export.md) | | | | ✓ | ✓ | | [Projects](project/index.md):<br>Manage [project access tokens](project/settings/project_access_tokens.md) (*11*) | | | | ✓ (*20*) | ✓ | | [Projects](project/index.md):<br>Manage [Project Operations](../operations/index.md) | | | | ✓ | ✓ | | [Projects](project/index.md):<br>Rename project | | | | ✓ | ✓ | diff --git a/lib/api/alert_management_alerts.rb b/lib/api/alert_management_alerts.rb index f57b7d00c81..9e28ee049d0 100644 --- a/lib/api/alert_management_alerts.rb +++ b/lib/api/alert_management_alerts.rb @@ -6,12 +6,21 @@ module API urgency :low params do - requires :id, types: [String, Integer], desc: 'The ID or URL-encoded path of the project' - requires :alert_iid, type: Integer, desc: 'The IID of the Alert' + requires :id, types: [String, Integer], desc: 'The ID or URL-encoded path of the project', + documentation: { example: 17 } + requires :alert_iid, type: Integer, desc: 'The IID of the Alert', + documentation: { example: 23 } end resource :projects, requirements: ::API::API::NAMESPACE_OR_PROJECT_REQUIREMENTS do namespace ':id/alert_management_alerts/:alert_iid/metric_images' do + desc 'Workhorse authorize metric image file upload' do + success code: 200 + failure [ + { code: 403, message: 'Forbidden' } + ] + tags %w[alert_management] + end post 'authorize' do authorize!(:upload_alert_management_metric_image, find_project_alert(request.params[:alert_iid])) @@ -29,13 +38,20 @@ module API end desc 'Upload a metric image for an alert' do - success Entities::MetricImage + consumes ['multipart/form-data'] + success code: 200, model: Entities::MetricImage + failure [ + { code: 403, message: 'Forbidden' } + ] + tags %w[alert_management] end params do requires :file, type: ::API::Validations::Types::WorkhorseFile, desc: 'The image file to be uploaded', documentation: { type: 'file' } - optional :url, type: String, desc: 'The url to view more metric info' - optional :url_text, type: String, desc: 'A description of the image or URL' + optional :url, type: String, desc: 'The url to view more metric info', + documentation: { example: 'https://example.com/metric' } + optional :url_text, type: String, desc: 'A description of the image or URL', + documentation: { example: 'An example metric' } end post do require_gitlab_workhorse! @@ -61,7 +77,14 @@ module API end end - desc 'Metric Images for alert' + desc 'Metric Images for alert' do + success code: 200, model: Entities::MetricImage + is_array true + failure [ + { code: 404, message: 'Not found' } + ] + tags %w[alert_management] + end get do alert = find_project_alert(params[:alert_iid]) @@ -73,12 +96,21 @@ module API end desc 'Update a metric image for an alert' do - success Entities::MetricImage + consumes ['multipart/form-data'] + success code: 200, model: Entities::MetricImage + failure [ + { code: 403, message: 'Forbidden' }, + { code: 422, message: 'Unprocessable entity' } + ] + tags %w[alert_management] end params do - requires :metric_image_id, type: Integer, desc: 'The ID of metric image' - optional :url, type: String, desc: 'The url to view more metric info' - optional :url_text, type: String, desc: 'A description of the image or URL' + requires :metric_image_id, type: Integer, desc: 'The ID of metric image', + documentation: { example: 42 } + optional :url, type: String, desc: 'The url to view more metric info', + documentation: { example: 'https://example.com/metric' } + optional :url_text, type: String, desc: 'A description of the image or URL', + documentation: { example: 'An example metric' } end put ':metric_image_id' do alert = find_project_alert(params[:alert_iid]) @@ -97,10 +129,16 @@ module API end desc 'Remove a metric image for an alert' do - success Entities::MetricImage + success code: 204, model: Entities::MetricImage + failure [ + { code: 403, message: 'Forbidden' }, + { code: 422, message: 'Unprocessable entity' } + ] + tags %w[alert_management] end params do - requires :metric_image_id, type: Integer, desc: 'The ID of metric image' + requires :metric_image_id, type: Integer, desc: 'The ID of metric image', + documentation: { example: 42 } end delete ':metric_image_id' do alert = find_project_alert(params[:alert_iid]) diff --git a/lib/api/api.rb b/lib/api/api.rb index 0e49103a880..3c88d2483d2 100644 --- a/lib/api/api.rb +++ b/lib/api/api.rb @@ -174,6 +174,7 @@ module API mount ::API::Admin::Ci::Variables mount ::API::Admin::InstanceClusters mount ::API::Admin::PlanLimits + mount ::API::AlertManagementAlerts mount ::API::Appearance mount ::API::Applications mount ::API::Avatar @@ -272,7 +273,6 @@ module API # Keep in alphabetical order mount ::API::Admin::BatchedBackgroundMigrations mount ::API::Admin::Sidekiq - mount ::API::AlertManagementAlerts mount ::API::AwardEmoji mount ::API::Boards mount ::API::Ci::JobArtifacts diff --git a/lib/api/entities/metric_image.rb b/lib/api/entities/metric_image.rb index fd5e3a62e40..3e4566832c9 100644 --- a/lib/api/entities/metric_image.rb +++ b/lib/api/entities/metric_image.rb @@ -3,7 +3,13 @@ module API module Entities class MetricImage < Grape::Entity - expose :id, :created_at, :filename, :file_path, :url, :url_text + expose :id, documentation: { type: 'integer', example: 23 } + expose :created_at, documentation: { type: 'dateTime', example: '2020-11-13T00:06:18.084Z' } + expose :filename, documentation: { type: 'string', example: 'file.png' } + expose :file_path, documentation: { type: 'string', + example: '/uploads/-/system/alert_metric_image/file/23/file.png' } + expose :url, documentation: { type: 'string', example: 'https://example.com/metric' } + expose :url_text, documentation: { type: 'string', example: 'An example metric' } end end end diff --git a/spec/tooling/docs/deprecation_handling_spec.rb b/spec/tooling/docs/deprecation_handling_spec.rb index 15dd69275c9..94c93d99b94 100644 --- a/spec/tooling/docs/deprecation_handling_spec.rb +++ b/spec/tooling/docs/deprecation_handling_spec.rb @@ -16,7 +16,7 @@ RSpec.describe Docs::DeprecationHandling do # Create dummy YAML data based on file name allow(YAML).to receive(:load_file) do |file_name| { - 'name' => file_name[/[a-z]*\.yml/], + 'title' => file_name[/[a-z]*\.yml/], 'announcement_milestone' => file_name[/\d+-\d+/].tr('-', '.') } end @@ -29,7 +29,7 @@ RSpec.describe Docs::DeprecationHandling do entries = arguments[:entries] expect(milestones).to eq(['14.10', '14.2']) - expect(entries.map { |e| e['name'] }).to eq(['a.yml', 'b.yml', 'c.yml']) + expect(entries.map { |e| e['title'] }).to eq(['a.yml', 'b.yml', 'c.yml']) end end diff --git a/tooling/docs/deprecation_handling.rb b/tooling/docs/deprecation_handling.rb index a620eac4c91..bcdf73e0044 100644 --- a/tooling/docs/deprecation_handling.rb +++ b/tooling/docs/deprecation_handling.rb @@ -22,7 +22,7 @@ module Docs entries = source_file_paths.flat_map do |file| YAML.load_file(file) end - entries = entries.sort_by { |d| d["name"] } + entries = entries.sort_by { |d| d["title"] } milestones = entries.map { |entry| entry[milestone_key_name] }.uniq milestones = VersionSorter.rsort(milestones) |