Remove superseded deprecation scripts (#55451)

Author: rachmari

.github/workflows/test.yml

@@ -57,7 +57,6 @@ jobs:
           - events
           - fixtures
           - frame
-          - ghes-releases
           - github-apps
           - graphql
           - landings

package.json

@@ -19,7 +19,6 @@
     "all-documents": "tsx src/content-render/scripts/all-documents/cli.ts",
     "analyze-text": "tsx src/search/scripts/analyze-text.ts",
     "analyze-comment": "tsx src/events/scripts/analyze-comment-cli.ts",
-    "archive-version": "tsx --max-old-space-size=16384 src/ghes-releases/scripts/archive-version.ts",
     "build": "next build",
     "check-content-type": "tsx src/workflows/check-content-type.ts",
     "check-github-github-links": "tsx src/links/scripts/check-github-github-links.ts",
@@ -76,7 +75,6 @@
     "ready-for-docs-review": "tsx src/workflows/ready-for-docs-review.ts",
     "release-banner": "tsx src/ghes-releases/scripts/release-banner.js",
     "reusables": "tsx src/content-render/scripts/reusables-cli.ts",
-    "remove-version-markup": "tsx src/ghes-releases/scripts/remove-version-markup.js",
     "rendered-content-link-checker": "tsx src/links/scripts/rendered-content-link-checker.ts",
     "rendered-content-link-checker-cli": "tsx src/links/scripts/rendered-content-link-checker-cli.ts",
     "rest-dev": "tsx src/rest/scripts/update-files.js",

src/ghes-releases/lib/release-templates/release-steps-1.md

@@ -54,15 +54,15 @@ To enable a new version of GHES on GitHub Docs, update the site's supported vers
 
   - [ ] For `supported`, prepend the new version. For example, if the array contains 3.9, 3.8, 3.7, and 3.6, add 3.10:
 
-     ```js
-     export const supported = ['3.10', '3.9', '3.8', '3.7', '3.6']
-     ```
+    ```js
+    export const supported = ["3.10", "3.9", "3.8", "3.7", "3.6"];
+    ```
 
   - [ ] For `releaseCandidate`, change the variable definition from `null` to the release version. For example, if the release version is 3.10:
 
-     ```js
-     export const releaseCandidate = '3.10'
-     ```
+    ```js
+    export const releaseCandidate = "3.10";
+    ```
 
   - [ ] Add and commit the changes.
 
@@ -71,7 +71,7 @@ To enable a new version of GHES on GitHub Docs, update the site's supported vers
   - [ ] Run the following script.
 
     ```shell
-    src/ghes-releases/scripts/sync-automated-pipeline-data.js
+    npm run deprecate-ghes -- pipelines
     ```
 
   - [ ] Add and commit the changes.
@@ -101,6 +101,7 @@ Our link checker validates links the site. If links are broken immediately after
 If you aren't familiar with the content with the broken link, consult the DRI for the content's focus area. See the [README](https://github.com/github/docs-content/blob/main/focus-areas/README.md) in `github/docs-content`.
 
 For broken links due to in-progress work elsewhere in the docs, you can comment out problematic versioning temporarily by:
+
 - using {% raw %}`{% comment %}`{% endraw %} tags in Liquid or
 - prepending `#` in YAML front matter.
 
@@ -118,9 +119,9 @@ For content from the OpenAPI schema, note the affected content with broken links
 
 1. Go to the [`index-general-search.yml` workflow](https://github.com/github/docs-internal/actions/workflows/index-general-search.yml)
 1. Click on the **Run workflow** drop down and set the following parameters:
-    - `Branch:` set to the name of the publication branch
-    - `Version` set to the version you're publishing (e.g., `ghes-3.12` if you're publishing GHES 3.12)
-    - `Languages` left as default (blank, all languages. If time is a concern, can also set to just `en` and wait for the workflow to automatically include the other languages in later runs)
+   - `Branch:` set to the name of the publication branch
+   - `Version` set to the version you're publishing (e.g., `ghes-3.12` if you're publishing GHES 3.12)
+   - `Languages` left as default (blank, all languages. If time is a concern, can also set to just `en` and wait for the workflow to automatically include the other languages in later runs)
 1. Click **Run workflow** and wait for the workflow to finish running, which can take up to 30 minutes.
 
 _Note_: After performing these steps, search indices will be automatically updated when the workflow runs on `main`, once every 4 hours. However, it will not do so until you first complete the steps above which will manually create a search index for the new release.
@@ -135,7 +136,7 @@ After your publication PR's are passing, complete the following maintenance **da
 
 1. Check out `main`, then pull the latest changes.
 
-1. Check out your publication branch,  <code>ghes-VERSION-rc</code>, then merge changes from `main`.
+1. Check out your publication branch, <code>ghes-VERSION-rc</code>, then merge changes from `main`.
 
 1. Push the changes.