Remove self-hosted update pages that now redirect

docs/self-hosted/deploy/docker-compose/upgrade.mdx

@@ -5,7 +5,7 @@ import {CURRENT_VERSION_STRING} from 'src/components/PreCodeBlock';
 This document describes the process to update a Docker Compose Sourcegraph instance. If you are unfamiliar with sourcegraph versioning or releases see our [general concepts documentation](/self-hosted/updates/).
 
 > <Callout type="note">
-> 	Always consult the [release notes](/self-hosted/updates/docker-compose) for the
+> 	Always consult the [release notes](https://sourcegraph.com/changelog/self-hosted/docker-compose) for the
 > 	versions your upgrade will pass over and end on.
 > </Callout>
 
@@ -74,7 +74,7 @@ To perform a multi-version upgrade via migrators [upgrade](/self-hosted/updates/
 
 1. **Check Upgrade Readiness**:
 
-    - Check the [upgrade notes](/self-hosted/updates/docker-compose#docker-compose-upgrade-notes) for the version range you're passing through.
+    - Check the [upgrade notes](https://sourcegraph.com/changelog/self-hosted/docker-compose) for the version range you're passing through.
     - Check the `Site Admin > Updates` page to determine [upgrade readiness](/self-hosted/updates/#upgrade-readiness).
 
 2. **Pull and merge upstream changes**:

docs/self-hosted/deploy/docker-single-container/index.mdx

@@ -156,7 +156,7 @@ From sourcegraph version 5.11 onwards, the Sourcegraph single container Docker i
 **Before performing a multi-version upgrade**:
 
 -   Read our [update policy](/self-hosted/updates/#update-policy) to learn about Sourcegraph updates.
--   Find the entries that apply to the version range you're passing through in the [update notes for Sourcegraph with Docker Single Container](/self-hosted/updates/server#multi-version-upgrade-procedure).
+-   Find the entries that apply to the version range you're passing through in the [update notes for Sourcegraph with Docker Single Container](https://sourcegraph.com/changelog/self-hosted/server).
 
 0. You must first shutdown the container instance via `docker stop [CONTAINER]`.
 1. Start a temporary Postgres container on top of the Postgres data directory used by the old `sourcegraph/server` image. You must use the _new_ postgresql-16-codeinsights image, which is based on the new Postgresql 16 image, and provides an automatic upgrade script to move from Postgresql 12 to Postgresql 16.
@@ -177,7 +177,7 @@ A [standard upgrade](/self-hosted/updates/#standard-upgrades) occurs between two
 **Before upgrading:**
 
 -   Read our [update policy](/self-hosted/updates/#update-policy) to learn about Sourcegraph updates.
--   Find the relevant entry for your update in the [update notes for single-container Sourcegraph with Docker](/self-hosted/updates/server).
+-   Find the relevant entry for your update in the [update notes for single-container Sourcegraph with Docker](https://sourcegraph.com/changelog/self-hosted/server).
 
 To update, just use the newer `sourcegraph/server:N.N.N` Docker image (where `N.N.N` is a patch or single minor release away your current version) in place of the older one, using the same Docker volumes. Your server's data will be migrated automatically if needed. You can always find the version number details of the latest release via the [technical changelog](/technical-changelog).
 
@@ -204,7 +204,7 @@ A [multi-version upgrade](/self-hosted/updates/#multi-version-upgrades) is a dow
 **Before performing a multi-version upgrade**:
 
 -   Read our [update policy](/self-hosted/updates/#update-policy) to learn about Sourcegraph updates.
--   Find the entries that apply to the version range you're passing through in the [update notes for Sourcegraph with Docker Single Container](/self-hosted/updates/server#multi-version-upgrade-procedure).
+-   Find the entries that apply to the version range you're passing through in the [update notes for Sourcegraph with Docker Single Container](https://sourcegraph.com/changelog/self-hosted/server).
 
 To perform a multi-version upgrade on a Sourcegraph instance running on Docker Single Container:
 

docs/self-hosted/deploy/kubernetes/index.mdx

@@ -1017,7 +1017,7 @@ When all pods have restarted and show as Running, you can browse to your Sourceg
 
 **Step 1:** Check Upgrade Readiness:
 
--   Check the [upgrade notes](/self-hosted/updates/kubernetes#kubernetes-upgrade-notes) for the version range you're passing through.
+-   Check the [upgrade notes](https://sourcegraph.com/changelog/self-hosted/kubernetes) for the version range you're passing through.
 -   Check the `Site Admin > Updates` page to determine [upgrade readiness](/self-hosted/updates/#upgrade-readiness).
 
 **Step 2:**

docs/self-hosted/deploy/kubernetes/upgrade.mdx

@@ -6,7 +6,7 @@ This guide is **not for use with Helm**. Please refer to the [Upgrading Sourcegr
 
 > **_⚠️ Attention:_**
 >
-> -   **_Always consult the [release notes](/self-hosted/updates/kubernetes) for the versions your upgrade will pass over and end on._**
+> -   **_Always consult the [release notes](https://sourcegraph.com/changelog/self-hosted/kubernetes) for the versions your upgrade will pass over and end on._**
 > -   _This guide assumes you have created a `release` branch following the [reference repositories docs](/self-hosted/deploy/repositories)_
 > -   **\*please see our [cautionary note](/self-hosted/updates/#best-practices) on upgrades**, if you have any concerns about running a multiversion upgrade, please reach out to us at [support@sourcegraph.com](mailto:support@sourcegraph.com) for advisement.\*
 
@@ -82,7 +82,7 @@ To perform a multi-version upgrade via migrators [upgrade](/self-hosted/updates/
 
 1. **Check Upgrade Readiness**:
 
-    - Check the [upgrade notes](/self-hosted/updates/kubernetes#kubernetes-upgrade-notes) for the version range you're passing through.
+    - Check the [upgrade notes](https://sourcegraph.com/changelog/self-hosted/kubernetes) for the version range you're passing through.
     - Check the `Site Admin > Updates` page to determine [upgrade readiness](/self-hosted/updates/#upgrade-readiness).
 
 2. **Pull and merge upstream changes**:

docs/self-hosted/deploy/machine-images/aws-ami.mdx

@@ -184,7 +184,7 @@ Please take time to review the following before proceeding with the upgrades:
 
 - [Technical changelog](/technical-changelog)
 - [Update policy](/self-hosted/updates#update-policy)
-- [Update notes](/self-hosted/updates/kubernetes)
+- [Update notes](https://sourcegraph.com/changelog/self-hosted/kubernetes)
 
 <Callout type="warning">Back up your volumes before each upgrade!</Callout>
 

docs/self-hosted/deploy/machine-images/gce.mdx

@@ -171,8 +171,8 @@ Please take time to review the following before proceeding with the upgrades:
 
 -   [Technical changelog](/technical-changelog)
 -   [Update policy](/self-hosted/updates#update-policy)
--   [Update notes](/self-hosted/updates/kubernetes)
--   [Multi-version upgrade procedure](/self-hosted/updates/kubernetes#multi-version-upgrade-procedure)
+-   [Update notes](https://sourcegraph.com/changelog/self-hosted/kubernetes)
+-   [Multi-version upgrade procedure](https://sourcegraph.com/changelog/self-hosted/kubernetes)
 
 IMPORTANT: **Back up your volumes before each upgrade**
 
@@ -228,7 +228,7 @@ You can terminate the stopped Sourcegraph Google Image instance once you have co
 
 <Callout type="warning">
 	You must follow the [multi-version upgrade
-	procedure](/self-hosted/updates/kubernetes#multi-version-upgrade-procedure) if you
+	procedure](https://sourcegraph.com/changelog/self-hosted/kubernetes) if you
 	are attempting a multi-version upgrade.
 </Callout>
 

docs/self-hosted/deploy/single-node/script.mdx

@@ -80,8 +80,8 @@ We recommend deploying your own reverse proxy to terminate TLS connections with
 
 -   [Technical changelog](/technical-changelog)
 -   [Update policy](/self-hosted/updates#update-policy)
--   [Update notes](/self-hosted/updates/kubernetes)
--   [Multi-version upgrade procedure](/self-hosted/updates/kubernetes#multi-version-upgrade-procedure)
+-   [Update notes](https://sourcegraph.com/changelog/self-hosted/kubernetes)
+-   [Multi-version upgrade procedure](https://sourcegraph.com/changelog/self-hosted/kubernetes)
 
 > Important: Back up your volumes before each upgrade
 

docs/self-hosted/how-to/precise-code-intel-worker-crashloopbackoff.mdx

@@ -2,7 +2,7 @@
 
 This document will discuss one of the main reasons why the `precise-code-intel-worker` goes into a `CrashLoopBackOff` state in a Kubernetes. It does not attempt to solve _all_ reasons why this state can happen.
 
-This commonly happens when upgrading from a Sourcegraph version prior to 3.22 to a later version and failing to deploy the MinIO container. This is because in [3.21 -> 3.22 we removed the `code intel bundle manager` and replaced it with `MinIO`.](/self-hosted/updates/kubernetes#3-21-3-22)
+This commonly happens when upgrading from a Sourcegraph version prior to 3.22 to a later version and failing to deploy the MinIO container. This is because in [3.21 -> 3.22 we removed the `code intel bundle manager` and replaced it with `MinIO`.](https://sourcegraph.com/changelog/self-hosted/kubernetes)
 
 ## Symptoms
 

docs/self-hosted/index.mdx

@@ -34,10 +34,10 @@ Get started running Sourcegraph on-prem.
 ## [Upgrade Sourcegraph](/self-hosted/updates)
 
 -   [Upgrade Overview](/self-hosted/updates/)
--   [Docker Compose upgrades](/self-hosted/updates/docker-compose)
--   [Kubernetes upgrades](/self-hosted/updates/kubernetes)
+-   [Docker Compose upgrades](https://sourcegraph.com/changelog/self-hosted/docker-compose)
+-   [Kubernetes upgrades](https://sourcegraph.com/changelog/self-hosted/kubernetes)
 -   [Pure Docker upgrades](/self-hosted/updates/pure-docker)
--   [Server upgrades](/self-hosted/updates/server)
+-   [Server upgrades](https://sourcegraph.com/changelog/self-hosted/server)
 -   [Migrator](/self-hosted/updates/migrator/)
 -   [Upgrading PostgreSQL](/self-hosted/postgres#upgrading-postgresql)
 

docs/self-hosted/updates/automatic.mdx

@@ -16,7 +16,7 @@ From **Sourcegraph 5.1 through 6.11.x**, multi-version upgrades could be perform
 
 1. Determine if your instance is ready to Upgrade:
     1. Check your Sourcegraph instances `Site admin > Updates` page. ([more info](/self-hosted/updates/#upgrade-readiness))
-    2. Consult upgrade notes for your deployment type accross the range of your upgrade. ([Kubernetes](/self-hosted/updates/kubernetes), [Docker-compose](/self-hosted/updates/docker-compose), [Server](/self-hosted/updates/server))
+    2. Consult upgrade notes for your deployment type accross the range of your upgrade. ([Kubernetes](https://sourcegraph.com/changelog/self-hosted/kubernetes), [Docker-compose](https://sourcegraph.com/changelog/self-hosted/docker-compose), [Server](https://sourcegraph.com/changelog/self-hosted/server))
 2. Merge the latest Sourcegraph release into your deployment manifests.
 3. With upstream changes to your manifests merged, start the new instance.