Update full docs links to use pretty URLs

All URLs skip .html, and no more need to use /ee

data/deprecations/14-0-approvals-endpoint.yml

@@ -8,7 +8,7 @@
   body: |  # (required) Do not modify this line, instead modify the lines below.
     To change the approvals required for a merge request, you should no longer use the `/approvals` API endpoint, which was deprecated in GitLab 14.0.
 
-    Instead, use the [`/approval_rules` endpoint](https://docs.gitlab.com/ee/api/merge_request_approvals.html#merge-request-level-mr-approvals) to [create](https://docs.gitlab.com/ee/api/merge_request_approvals.html#create-merge-request-level-rule) or [update](https://docs.gitlab.com/ee/api/merge_request_approvals.html#update-merge-request-level-rule) the approval rules for a merge request.
+    Instead, use the [`/approval_rules` endpoint](https://docs.gitlab.com/api/merge_request_approvals/#merge-request-level-mr-approvals) to [create](https://docs.gitlab.com/api/merge_request_approvals/#create-merge-request-level-rule) or [update](https://docs.gitlab.com/api/merge_request_approvals/#update-merge-request-level-rule) the approval rules for a merge request.
   end_of_support_milestone:
   tiers: Premium
   documentation_url: https://docs.gitlab.com/ee/api/merge_request_approvals.html

data/deprecations/14-0-nfs-fot-git-repository-storage.yml

@@ -7,11 +7,11 @@
 
     Gitaly Cluster offers tremendous benefits for our customers such as:
 
-    - [Variable replication factors](https://docs.gitlab.com/ee/administration/gitaly/#replication-factor).
-    - [Strong consistency](https://docs.gitlab.com/ee/administration/gitaly/#strong-consistency).
-    - [Distributed read capabilities](https://docs.gitlab.com/ee/administration/gitaly/#distributed-reads).
+    - [Variable replication factors](https://docs.gitlab.com/administration/gitaly/#replication-factor).
+    - [Strong consistency](https://docs.gitlab.com/administration/gitaly/#strong-consistency).
+    - [Distributed read capabilities](https://docs.gitlab.com/administration/gitaly/#distributed-reads).
 
-    We encourage customers currently using NFS for Git repositories to plan their migration by reviewing our documentation on [migrating to Gitaly Cluster](https://docs.gitlab.com/ee/administration/gitaly/#migrate-to-gitaly-cluster).
+    We encourage customers currently using NFS for Git repositories to plan their migration by reviewing our documentation on [migrating to Gitaly Cluster](https://docs.gitlab.com/administration/gitaly/#migrate-to-gitaly-cluster).
 
   reporter: mjwood
   stage: create

data/deprecations/14-10-dependency-scanning-default-java-version.yml

@@ -4,7 +4,7 @@
   breaking_change: true
   reporter: NicoleSchwartz
   body: |
-    In GitLab 15.0, for Dependency Scanning, the default version of Java that the scanner expects will be updated from 11 to 17. Java 17 is [the most up-to-date Long Term Support (LTS) version](https://en.wikipedia.org/wiki/Java_version_history). Dependency scanning continues to support the same [range of versions (8, 11, 13, 14, 15, 16, 17)](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#supported-languages-and-package-managers), only the default version is changing. If your project uses the previous default of Java 11, be sure to [set the `DS_Java_Version` variable to match](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuring-specific-analyzers-used-by-dependency-scanning).
+    In GitLab 15.0, for Dependency Scanning, the default version of Java that the scanner expects will be updated from 11 to 17. Java 17 is [the most up-to-date Long Term Support (LTS) version](https://en.wikipedia.org/wiki/Java_version_history). Dependency scanning continues to support the same [range of versions (8, 11, 13, 14, 15, 16, 17)](https://docs.gitlab.com/user/application_security/dependency_scanning/#supported-languages-and-package-managers), only the default version is changing. If your project uses the previous default of Java 11, be sure to [set the `DS_Java_Version` variable to match](https://docs.gitlab.com/user/application_security/dependency_scanning/#configuring-specific-analyzers-used-by-dependency-scanning).
 # 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-10-old-search-migration-removal.yml

@@ -6,7 +6,7 @@
     As Advanced Search migrations usually require support multiple code paths for a long period of time,
     it's important to clean those up when we safely can. We use GitLab major version upgrades as a safe
     time to remove backward compatibility for indices that have not been fully migrated. See the
-    [upgrade documentation](https://docs.gitlab.com/ee/update/#upgrading-to-a-new-major-version) for details.
+    [upgrade documentation](https://docs.gitlab.com/update/#upgrading-to-a-new-major-version) for details.
   stage: enablement
   tiers: premium, ultimate
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/359133

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

@@ -3,7 +3,7 @@
   removal_milestone: "15.0"
   breaking_change: true
   body: |
-    The syntax of [GitLabs database](https://docs.gitlab.com/omnibus/settings/database.html)
+    The syntax of [GitLabs database](https://docs.gitlab.com/omnibus/settings/database/)
     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.
 

data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml

@@ -5,7 +5,7 @@
   body: |  # Do not modify this line, instead modify the lines below.
     The `omniauth-kerberos` gem will be removed in our next major release, GitLab 15.0.
 
-    This gem has not been maintained and has very little usage. We therefore plan to remove support for this authentication method and recommend using the Kerberos [SPNEGO](https://en.wikipedia.org/wiki/SPNEGO) integration instead. You can follow the [upgrade instructions](https://docs.gitlab.com/ee/integration/kerberos.html#upgrading-from-password-based-to-ticket-based-kerberos-sign-ins) to upgrade from the `omniauth-kerberos` integration to the supported one.
+    This gem has not been maintained and has very little usage. We therefore plan to remove support for this authentication method and recommend using the Kerberos [SPNEGO](https://en.wikipedia.org/wiki/SPNEGO) integration instead. You can follow the [upgrade instructions](https://docs.gitlab.com/integration/kerberos/#upgrading-from-password-based-to-ticket-based-kerberos-sign-ins) to upgrade from the `omniauth-kerberos` integration to the supported one.
 
     Note that we are not deprecating the Kerberos SPNEGO integration, only the old password-based Kerberos integration.
   stage: Foundations

data/deprecations/14-5-certificate-based-integration-with-kubernetes-saas.yml

@@ -6,14 +6,14 @@
     The certificate-based integration with Kubernetes will be [deprecated and removed](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/). As a GitLab.com user, on new namespaces, you will no longer be able to integrate GitLab and your cluster using the certificate-based approach as of GitLab 15.0. The integration for current users will be enabled per namespace.
 
     For a more robust, secure, forthcoming, and reliable integration with Kubernetes, we recommend you use the
-    [agent for Kubernetes](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. [How do I migrate?](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html)
+    [agent for Kubernetes](https://docs.gitlab.com/user/clusters/agent/) to connect Kubernetes clusters with GitLab. [How do I migrate?](https://docs.gitlab.com/user/infrastructure/clusters/migrate_to_gitlab_agent/)
 
     Although an explicit removal date is set, we don't plan to remove this feature until the new solution has feature parity.
     For more information about the blockers to removal, see [this issue](https://gitlab.com/gitlab-org/configure/general/-/issues/199).
 
     For updates and details about this deprecation, follow [this epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8).
 
-    GitLab Self-Managed customers can still use the feature [with a feature flag](https://docs.gitlab.com/ee/update/deprecations.html#self-managed-certificate-based-integration-with-kubernetes).
+    GitLab Self-Managed customers can still use the feature [with a feature flag](https://docs.gitlab.com/update/deprecations/#self-managed-certificate-based-integration-with-kubernetes).
   stage: Configure
   tiers: [Free, Premium, Ultimate]
   issue_url: 'https://gitlab.com/groups/gitlab-org/configure/-/epics/8'

data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml

@@ -9,12 +9,12 @@
   body: |
     The certificate-based integration with Kubernetes [will be deprecated and removed](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/).
 
-    For GitLab Self-Managed, we are introducing the [feature flag](https://docs.gitlab.com/ee/administration/feature_flags.html#enable-or-disable-the-feature) `certificate_based_clusters` in GitLab 15.0 so you can keep your certificate-based integration enabled. However, the feature flag will be disabled by default, so this change is a **breaking change**.
+    For GitLab Self-Managed, we are introducing the [feature flag](https://docs.gitlab.com/administration/feature_flags/#enable-or-disable-the-feature) `certificate_based_clusters` in GitLab 15.0 so you can keep your certificate-based integration enabled. However, the feature flag will be disabled by default, so this change is a **breaking change**.
 
     In GitLab 19.0 we will remove both the feature and its related code. Until the final removal in 19.0, features built on this integration will continue to work, if you enable the feature flag. Until the feature is removed, GitLab will continue to fix security and critical issues as they arise.
 
     For a more robust, secure, forthcoming, and reliable integration with Kubernetes, we recommend you use the
-    [agent for Kubernetes](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. [How do I migrate?](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html)
+    [agent for Kubernetes](https://docs.gitlab.com/user/clusters/agent/) to connect Kubernetes clusters with GitLab. [How do I migrate?](https://docs.gitlab.com/user/infrastructure/clusters/migrate_to_gitlab_agent/)
 
     Although an explicit removal date is set, we don't plan to remove this feature until the new solution has feature parity.
     For more information about the blockers to removal, see [this issue](https://gitlab.com/gitlab-org/configure/general/-/issues/199).

data/deprecations/14-5-deprecation-versions-packagetype.yml

@@ -3,7 +3,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 part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `Version` type for the basic `PackageType` type and moved it to [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/#packagedetailstype).
+    As part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `Version` type for the basic `PackageType` type and moved it to [`PackageDetailsType`](https://docs.gitlab.com/api/graphql/reference/#packagedetailstype).
 
     In milestone 15.0, we will completely remove `Version` from `PackageType`.
   stage: package

data/deprecations/14-5-disable_strict_host_key_checking.yml

@@ -3,7 +3,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.
-    In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner `config.toml` file. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh.html#security), controls whether or not to use strict host key checking with the SSH executor.
+    In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner `config.toml` file. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh/#security), controls whether or not to use strict host key checking with the SSH executor.
 
     In GitLab 15.0 and later, the default value for this configuration option will change from `true` to `false`. This means that strict host key checking will be enforced when using the GitLab Runner SSH executor.
   stage: Verify

data/deprecations/14-5-package-container-registry-api-group-update.yml

@@ -3,7 +3,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.
-    In milestone 15.0, support for the `tags` and `tags_count` parameters will be removed from the container registry API that [gets registry repositories from a group](https://docs.gitlab.com/ee/api/container_registry.html#within-a-group).
+    In milestone 15.0, support for the `tags` and `tags_count` parameters will be removed from the container registry API that [gets registry repositories from a group](https://docs.gitlab.com/api/container_registry/#within-a-group).
 
     The `GET /groups/:id/registry/repositories` endpoint will remain, but won't return any info about tags. To get the info about tags, you can use the existing `GET /registry/repositories/:id` endpoint, which will continue to support the `tags` and `tag_count` options as it does today. The latter must be called once per image repository.
   stage: Package

data/deprecations/14-5-remove-pipelines-from-version-field.yml

@@ -3,7 +3,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.
-    In GraphQL, there are two `pipelines` fields that you can use in a [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/#packagedetailstype) to get the pipelines for package versions:
+    In GraphQL, there are two `pipelines` fields that you can use in a [`PackageDetailsType`](https://docs.gitlab.com/api/graphql/reference/#packagedetailstype) to get the pipelines for package versions:
 
     - The `versions` field's `pipelines` field. This returns all the pipelines associated with all the package's versions, which can pull an unbounded number of objects in memory and create performance concerns.
     - The `pipelines` field of a specific `version`. This returns only the pipelines associated with that single package version.

data/deprecations/14-6-Enforce-validation-of-security-schemas.yml

@@ -6,7 +6,7 @@
     versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
     against the schema version declared in the report will also no longer be supported in GitLab 15.0.
 
-    Security tools that [integrate with GitLab by outputting security reports](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    Security tools that [integrate with GitLab by outputting security reports](https://docs.gitlab.com/development/integrations/secure/#report)
     as pipeline job artifacts are affected. You must ensure that all output reports adhere to the correct
     schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate
     against the declared schema version will not be processed, and vulnerability

data/deprecations/14-6-container-scanning-schemas-below-14.yml

@@ -6,7 +6,7 @@
     versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
     against the schema version declared in the report will also no longer be supported in GitLab 15.0.
 
-    Third-party tools that [integrate with GitLab by outputting a container scanning security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    Third-party tools that [integrate with GitLab by outputting a container scanning security report](https://docs.gitlab.com/development/integrations/secure/#report)
     as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate against the declared schema version will not be processed, and vulnerability findings will not display in MRs, pipelines, or Vulnerability Reports.
 
     To help with the transition, from GitLab 14.10, non-compliant reports will display a

data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml

@@ -6,7 +6,7 @@
     below version 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
     against the schema version declared in the report will also no longer be supported in GitLab 15.0.
 
-    Third-party tools that [integrate with GitLab by outputting a coverage guided fuzzing security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    Third-party tools that [integrate with GitLab by outputting a coverage guided fuzzing security report](https://docs.gitlab.com/development/integrations/secure/#report)
     as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct
     schema with a minimum version of 14.0.0. Any reports with a lower version or that fail to validate
     against the declared schema version will not be processed, and vulnerability

data/deprecations/14-6-dast-schemas-below-14.yml

@@ -6,7 +6,7 @@
     versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
     against the schema version declared in the report will also no longer be supported as of GitLab 15.0.
 
-    Third-party tools that [integrate with GitLab by outputting a DAST security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    Third-party tools that [integrate with GitLab by outputting a DAST security report](https://docs.gitlab.com/development/integrations/secure/#report)
     as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct
     schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate
     against the declared schema version will not be processed, and vulnerability

data/deprecations/14-6-dependency-scanning-schemas-below-14.yml

@@ -6,7 +6,7 @@
     versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
     against the schema version declared in the report will also no longer be supported as of GitLab 15.0.
 
-    Third-party tools that [integrate with GitLab by outputting a Dependency scanning security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    Third-party tools that [integrate with GitLab by outputting a Dependency scanning security report](https://docs.gitlab.com/development/integrations/secure/#report)
     as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct
     schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate
     against the declared schema version will not be processed, and vulnerability

data/deprecations/14-6-sast-schemas-below-14.yml

@@ -6,7 +6,7 @@
     versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
     against the schema version declared in the report will also no longer be supported as of GitLab 15.0.
 
-    Third-party tools that [integrate with GitLab by outputting a SAST security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    Third-party tools that [integrate with GitLab by outputting a SAST security report](https://docs.gitlab.com/development/integrations/secure/#report)
     as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct
     schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate
     against the declared schema version will not be processed, and vulnerability

data/deprecations/14-6-secret-detection-schemas-below-14.yml

@@ -6,7 +6,7 @@
     versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
     against the schema version declared in the report will also no longer be supported as of GitLab 15.0.
 
-    Third-party tools that [integrate with GitLab by outputting a Secret detection security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    Third-party tools that [integrate with GitLab by outputting a Secret detection security report](https://docs.gitlab.com/development/integrations/secure/#report)
     as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct
     schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate
     against the declared schema version will not be processed, and vulnerability

data/deprecations/14-7-deprecate-static-site-editor.yml

@@ -2,9 +2,9 @@
   announcement_milestone: "14.7"  # The milestone when this feature was first announced as deprecated.
   removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
   body: |  # Do not modify this line, instead modify the lines below.
-    The Static Site Editor will no longer be available starting in GitLab 15.0. Improvements to the Markdown editing experience across GitLab will deliver similiar benefit but with a wider reach. Incoming requests to the Static Site Editor will be redirected to the [Web IDE](https://docs.gitlab.com/ee/user/project/web_ide/).
+    The Static Site Editor will no longer be available starting in GitLab 15.0. Improvements to the Markdown editing experience across GitLab will deliver similiar benefit but with a wider reach. Incoming requests to the Static Site Editor will be redirected to the [Web IDE](https://docs.gitlab.com/user/project/web_ide/).
 
-    Current users of the Static Site Editor can view the [documentation](https://docs.gitlab.com/ee/user/project/web_ide/) for more information, including how to remove the configuration files from existing projects.
+    Current users of the Static Site Editor can view the [documentation](https://docs.gitlab.com/user/project/web_ide/) for more information, including how to remove the configuration files from existing projects.
 # 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: [Free, Premium, 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]