feat(docs) update /changelog url to /technical-changelog (#708)

<!-- Explain the changes introduced in your PR -->

## Pull Request approval

Although pull request approval is not enforced for this repository in
order to reduce friction, merging without a review will generate a
ticket for the docs team to review your changes. So if possible, have
your pull request approved before merging.

Author: BolajiOlajide

.gitignore

@@ -44,4 +44,4 @@ next-env.d.ts
 .idea
 
 # We ignore the generated file as it should always be generated
-public/changelog.rss
+public/technical-changelog.rss

dev/rss.js

@@ -3,7 +3,7 @@ const fs = require('fs');
 const path = require('path');
 
 const loadChangelog = () => {
-    const changelogPath = path.join(__dirname, '..', 'docs', 'CHANGELOG.mdx');
+    const changelogPath = path.join(__dirname, '..', 'docs', 'technical-changelog.mdx');
     return fs.readFileSync(changelogPath, 'utf8');
 }
 
@@ -36,7 +36,7 @@ const generateRssFeed = () => {
         updated: date,
         generator: 'Sourcegraph RSS Feed',
         feedLinks: {
-            rss2: `${siteURL}/changelog.rss`,
+            rss2: `${siteURL}/technical-changelog.rss`,
         },
         author: {
             name: 'Sourcegraph',
@@ -55,7 +55,7 @@ const generateRssFeed = () => {
             continue;
         }
         const tag = comment.version.replace('v', '');
-        const versionDocLink = `${siteURL}/CHANGELOG#${comment.version.replaceAll('.', '')}`;
+        const versionDocLink = `${siteURL}/technical-changelog#${comment.version.replaceAll('.', '')}`;
         feed.addItem({
             title: `Sourcegraph ${tag}`,
             id: comment.version,
@@ -65,7 +65,7 @@ const generateRssFeed = () => {
         });
     }
 
-    fs.writeFileSync(path.join(__dirname, '../public/changelog.rss'), feed.rss2());
+    fs.writeFileSync(path.join(__dirname, '../public/technical-changelog.rss'), feed.rss2());
 }
 
 module.exports = { generateRssFeed }

docs/admin/deploy/docker-single-container/index.mdx

@@ -147,7 +147,7 @@ A [standard upgrade](/admin/updates/#standard-upgrades) occurs between two minor
 - Read our [update policy](/admin/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](/admin/updates/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 [changelog](/CHANGELOG).
+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).
 
 ### Multi-version upgrades
 

docs/admin/deploy/machine-images/aws-ami.mdx

@@ -174,7 +174,7 @@ Now that your instance is confirmed to be working, and you have HTTPS working th
 
 Please take time to review the following before proceeding with the upgrades:
 
-- [Changelog](/CHANGELOG)
+- [Technical changelog](/technical-changelog)
 - [Update policy](/admin/updates#update-policy)
 - [Update notes](/admin/updates/kubernetes)
 

docs/admin/deploy/machine-images/gce.mdx

@@ -132,7 +132,7 @@ As a result, setting up a static IP for your Sourcegraph instance is strongly re
 
 Please take time to review the following before proceeding with the upgrades:
 
-- [Changelog](/CHANGELOG)
+- [Technical changelog](/technical-changelog)
 - [Update policy](/admin/updates#update-policy)
 - [Update notes](/admin/updates/kubernetes)
 - [Multi-version upgrade procedure](/admin/updates/kubernetes#multi-version-upgrade-procedure)

docs/admin/deploy/single-node/script.mdx

@@ -72,7 +72,7 @@ Sourcegraph will be available on ports 80 and 443 (using a self signed certifica
 We recommend deploying your own reverse proxy to terminate TLS connections with a properly signed certificate.
 
 ## Upgrade
-- [Changelog](/CHANGELOG)
+- [Technical changelog](/technical-changelog)
 - [Update policy](/admin/updates#update-policy)
 - [Update notes](/admin/updates/kubernetes)
 - [Multi-version upgrade procedure](/admin/updates/kubernetes#multi-version-upgrade-procedure)

docs/admin/how-to/site-admin-quickstart.mdx

@@ -23,7 +23,7 @@ Regardless of the deployment option you choose, Sourcegraph can be self-hosted l
 
 
 ## Updating your instance
-New versions of Sourcegraph are released monthly (with patches released in between, as needed). New updates are announced in the [Sourcegraph blog](https://about.sourcegraph.com/blog), and comprehensive update notes are available in the [changelog](/CHANGELOG).
+New versions of Sourcegraph are released monthly (with patches released in between, as needed). New updates are announced in the [Sourcegraph blog](https://about.sourcegraph.com/blog), and comprehensive update notes are available in the [technical changelog](/technical-changelog).
 
 To check the current version of your instance, go to **User menu > Site admin > Updates**.
 

docs/admin/migration/3_30.mdx

@@ -15,6 +15,6 @@ The 3.30 release introduced a `pgsql` and `codeinteldb` base image change from d
 This caused corruption in indexes that have collatable key columns (e.g. any index with a `text` column).
 Read more about this [here](https://postgresql.verite.pro/blog/2018/08/27/glibc-upgrade.html).
 
-After we found the root-cause of the [issues many customers were seeing](https://github.com/sourcegraph/sourcegraph/issues/23288), we cut [a patch release, 3.30.3](/CHANGELOG#3-30-3), that reverted the images to be based on debian, buying us time to change the alpine based version of the images to [reindex affected indexes on startup, before accepting new connections](https://github.com/sourcegraph/sourcegraph/issues/23310).
+After we found the root-cause of the [issues many customers were seeing](https://github.com/sourcegraph/sourcegraph/issues/23288), we cut [a patch release, 3.30.3](/technical-changelog#3-30-3), that reverted the images to be based on debian, buying us time to change the alpine based version of the images to [reindex affected indexes on startup, before accepting new connections](https://github.com/sourcegraph/sourcegraph/issues/23310).
 
 However, this means that after fixing the corrupt indexes on the alpine images in the affected releases, upgrading to debian based images in 3.30.3 will cause index corruption again. For this reason, **do not upgrade to 3.30.3** after fixing corrupt Postgres indexes. Instead, [please upgrade directly to 3.31](/admin/migration/3_31).

docs/admin/updates/docker_compose.mdx

@@ -5,7 +5,7 @@ This page lists the changes that are relevant for upgrading Sourcegraph on **Doc
 For upgrade procedures or general info about sourcegraph versioning see the links below:
 - [Docker Compose Upgrade Procedures](/admin/deploy/docker-compose/upgrade)
 - [General Upgrade Info](/admin/updates/)
-- [Product changelog](/CHANGELOG)
+- [Technical changelog](/technical-changelog)
 
 > ***Attention:** These notes may contain relevant information about the infrastructure update such as resource requirement changes or versions of depencies (Docker, Docker Compose, externalized databases).*
 >

docs/admin/updates/index.mdx

@@ -4,7 +4,7 @@ This page is intended as an entry point into Sourcegraph versioning, upgrades, a
 
 **If you are already familiar with Sourcegraph upgrades [skip to instance specific procedures](#instance-specific-procedures).**
 
-> *Note: For product update notes, please refer to the [changelog](/CHANGELOG).*
+> *Note: For product update notes, please refer to the [technical changelog](/technical-changelog).*
 
 ## General concepts