Merge branch 'update-deprecations-whitespace' into 'master'

Remove space from deprecation filename

See merge request gitlab-org/gitlab!77276

data/deprecations/14-3-database-deprecate-legacy-database-conf.yml

@@ -5,11 +5,11 @@
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
   breaking_change: true
   body: |
-   The syntax of [GitLabs database](https://docs.gitlab.com/omnibus/settings/database.html)
-   configuration located in `database.yml` is changing and the legacy format is deprecated. The legacy format
-   supported using a single PostgreSQL adapter, whereas the new format is changing to support multiple databases. The `main:` database needs to be defined as a first configuration item.
-   
-   This deprecation mainly impacts users compiling GitLab from source because Omnibus will handle this configuration automatically.
+    The syntax of [GitLabs database](https://docs.gitlab.com/omnibus/settings/database.html)
+    configuration located in `database.yml` is changing and the legacy format is deprecated. The legacy format
+    supported using a single PostgreSQL adapter, whereas the new format is changing to support multiple databases. The `main:` database needs to be defined as a first configuration item.
+
+    This deprecation mainly impacts users compiling GitLab from source because Omnibus will handle this configuration automatically.
   stage: Enablement
   tiers: [Core, Premium, Ultimate]
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/338182

data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml

@@ -10,4 +10,3 @@
   stage: Verify
   tiers: [Core, Premium, Ultimate]
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/345347
-

data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml

@@ -6,7 +6,7 @@
   breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     We are changing how the date filter works in Value Stream Analytics. Instead of filtering by the time that the issue or merge request was created, the date filter will filter by the end event time of the given stage. This will result in completely different figures after this change has rolled out.
-    
+
     If you monitor Value Stream Analytics metrics and rely on the date filter, to avoid losing data, you must save the data prior to this change.
   stage: manage # (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]

data/deprecations/14-6-deprecate-types.yml

@@ -5,7 +5,7 @@
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
   breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
-   The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines that use these keywords will stop working, so you must switch to `stage` and `stages`, which have the same behavior.
+    The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines that use these keywords will stop working, so you must switch to `stage` and `stages`, which have the same behavior.
 # The following items are not published on the docs page, but may be used in the future.
   stage: # (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]

data/deprecations/14-6-deprecation-license-compliance-api-terms.yml

@@ -4,9 +4,9 @@
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
   breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
-    We deprecated legacy names for approval status of license policy (blacklisted, approved) in the `managed_licenses` API but they are still used in our API queries and responses. They will be removed in 15.0. 
+    We deprecated legacy names for approval status of license policy (blacklisted, approved) in the `managed_licenses` API but they are still used in our API queries and responses. They will be removed in 15.0.
 
-    If you are using our License Compliance API you should stop using the `approved` and `blacklisted` query parameters, they are now `allowed` and `denied`. In 15.0 the responses will also stop using `approved` and `blacklisted` so you need to adjust any of your custom tools to use the old and new values so they do not break with the 15.0 release. 
+    If you are using our License Compliance API you should stop using the `approved` and `blacklisted` query parameters, they are now `allowed` and `denied`. In 15.0 the responses will also stop using `approved` and `blacklisted` so you need to adjust any of your custom tools to use the old and new values so they do not break with the 15.0 release.
 # The following items are not published on the docs page, but may be used in the future.
   stage: secure # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
   tiers: ultimate # (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]

data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml

@@ -4,7 +4,7 @@
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
   breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
-    As of 14.6 bundler-audit is being deprecated from Dependency Scanning. It will continue to be in our CI/CD template while deprecated. We are removing bundler-audit from Dependency Scanning on May 22, 2022 in 15.0. After this removal Ruby scanning functionality will not be affected as it is still being covered by Gemnasium. 
+    As of 14.6 bundler-audit is being deprecated from Dependency Scanning. It will continue to be in our CI/CD template while deprecated. We are removing bundler-audit from Dependency Scanning on May 22, 2022 in 15.0. After this removal Ruby scanning functionality will not be affected as it is still being covered by Gemnasium.
 
     If you have explicitly excluded bundler-audit using DS_EXCLUDED_ANALYZERS you will need to clean up (remove the reference) in 15.0. If you have customized your pipeline's Dependency Scanning configuration, for example to edit the `bundler-audit-dependency_scanning` job, you will want to switch to gemnasium-dependency_scanning before removal in 15.0, to prevent your pipeline from failing. If you have not used the DS_EXCLUDED_ANALYZERS to reference bundler-audit, or customized your template specifically for bundler-audit, you will not need to take action.
 # The following items are not published on the docs page, but may be used in the future.

data/deprecations/15-0-deprecation-versions-packagetype.yml

@@ -11,4 +11,3 @@
   stage: package
   tiers: Free
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/327453
-

doc/update/deprecations.md

@@ -138,9 +138,9 @@ Planned removal: 2022-05-22
 
 ### Deprecate legacy approval status names from License Compliance API
 
-We deprecated legacy names for approval status of license policy (blacklisted, approved) in the `managed_licenses` API but they are still used in our API queries and responses. They will be removed in 15.0. 
+We deprecated legacy names for approval status of license policy (blacklisted, approved) in the `managed_licenses` API but they are still used in our API queries and responses. They will be removed in 15.0.
 
-If you are using our License Compliance API you should stop using the `approved` and `blacklisted` query parameters, they are now `allowed` and `denied`. In 15.0 the responses will also stop using `approved` and `blacklisted` so you need to adjust any of your custom tools to use the old and new values so they do not break with the 15.0 release. 
+If you are using our License Compliance API you should stop using the `approved` and `blacklisted` query parameters, they are now `allowed` and `denied`. In 15.0 the responses will also stop using `approved` and `blacklisted` so you need to adjust any of your custom tools to use the old and new values so they do not break with the 15.0 release.
 
 Announced: 2021-12-22
 Planned removal: 2022-05-22
@@ -164,7 +164,7 @@ Planned removal: 2022-05-22
 
 ### Deprecation of bundler-audit Dependency Scanning tool
 
-As of 14.6 bundler-audit is being deprecated from Dependency Scanning. It will continue to be in our CI/CD template while deprecated. We are removing bundler-audit from Dependency Scanning on May 22, 2022 in 15.0. After this removal Ruby scanning functionality will not be affected as it is still being covered by Gemnasium. 
+As of 14.6 bundler-audit is being deprecated from Dependency Scanning. It will continue to be in our CI/CD template while deprecated. We are removing bundler-audit from Dependency Scanning on May 22, 2022 in 15.0. After this removal Ruby scanning functionality will not be affected as it is still being covered by Gemnasium.
 
 If you have explicitly excluded bundler-audit using DS_EXCLUDED_ANALYZERS you will need to clean up (remove the reference) in 15.0. If you have customized your pipeline's Dependency Scanning configuration, for example to edit the `bundler-audit-dependency_scanning` job, you will want to switch to gemnasium-dependency_scanning before removal in 15.0, to prevent your pipeline from failing. If you have not used the DS_EXCLUDED_ANALYZERS to reference bundler-audit, or customized your template specifically for bundler-audit, you will not need to take action.