remove 3.5 markup (#39007)

Co-authored-by: Laura Coursen <lecoursen@github.com>

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md

@@ -45,7 +45,7 @@ In the global navigation menu, you can access the top repositories and teams you
 In the left sidebar of your dashboard, you can access the top repositories and teams you use.
 {% endif %}
 
-The list of top repositories is automatically generated, and can include any repository you have interacted with, whether it's owned directly by your account or not. Interactions include making commits and opening or commenting on issues and pull requests. The list of top repositories cannot be edited, but repositories will drop off the list {% ifversion ghes < 3.6 or ghae < 3.6 %}4 months{% else %}1 year{% endif %} after you last interacted with them.
+The list of top repositories is automatically generated, and can include any repository you have interacted with, whether it's owned directly by your account or not. Interactions include making commits and opening or commenting on issues and pull requests. The list of top repositories cannot be edited, but repositories will drop off the list 1 year after you last interacted with them.
 
 You can also find a list of your recently visited repositories, teams, and project boards when you click into the search bar at the top of any page on {% data variables.product.product_name %}.
 

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md

@@ -33,14 +33,7 @@ If you have low vision, you may benefit from a high contrast theme, with greater
 1. Click the theme you'd like to use.
     - If you chose a single theme, click a theme.
 
-      {%- ifversion ghes = 3.5 %}
-      {% note %}
       
-      **Note**: The light high contrast theme was unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The theme is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
-
-      For more information about determining the version of {% data variables.product.product_name %} you're using, see "[AUTOTITLE](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
-      {% endnote %}
-      {%- endif %}
 
     - If you chose to follow your system settings, click a day theme and a night theme.{% ifversion fpt or ghec %}
     - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[AUTOTITLE](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}

content/actions/creating-actions/metadata-syntax-for-github-actions.md

@@ -358,7 +358,7 @@ runs:
         last_name: Octocat
 ```
 
-{% ifversion ghes > 3.5 or ghae > 3.5 %}
+{% ifversion ghes or ghae %}
 
 #### `runs.steps[*].continue-on-error`
 

content/actions/learn-github-actions/contexts.md

@@ -199,9 +199,7 @@ The `github` context contains information about the workflow run and the event t
 | `github.retention_days` | `string` | The number of days that workflow run logs and artifacts are kept. |
 | `github.run_id` | `string` | {% data reusables.actions.run_id_description %} |
 | `github.run_number` | `string` | {% data reusables.actions.run_number_description %} |
-{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}
 | `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
-{%- endif %}
 | `github.secret_source` | `string` | The source of a secret used in a workflow. Possible values are `None`, `Actions`{% ifversion fpt or ghec %}, `Codespaces`{% endif %}, or `Dependabot`. |
 | `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. |
 | `github.sha` | `string` | {% data reusables.actions.github_sha_description %} |

content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md

@@ -51,11 +51,12 @@ Your instance validates the hostnames for proxy exclusion using the list of IANA
      - When you exclude additional unregistered TLDs, you must use `.` as a wildcard prefix. If the TLD is `tentacle`, you must exclude `.tentacle`. You cannot exclude an unregistered TLD without the preceding `.`.
    - You can exclude a full, valid IPv4 or IPv6 address.
    - You cannot exclude an IPv4 or IPv6 address using a preceding or trailing dot as a wildcard.
+
 {% data reusables.enterprise_management_console.save-settings %}
 
 ## Excluding additional unregistered TLDs from the proxy
 
-{% ifversion ghes < 3.9 %}In {% data variables.product.product_name %} 3.{% ifversion ghes = 3.5 %}5.15{% elsif ghes = 3.6 %}6.11{% elsif ghes = 3.7%}7.8{% elsif ghes = 3.8 %}8.1{% endif %} and later, you{% elsif ghes > 3.8 %}You{% endif %} can configure your instance's proxy settings to exclude unregistered TLDs that aren't specified in the [list of TLDs](https://data.iana.org/TLD/tlds-alpha-by-domain.txt) on the IANA website.
+{% ifversion ghes < 3.9 %}In {% data variables.product.product_name %} 3.{% ifversion ghes = 3.6 %}6.11{% elsif ghes = 3.7%}7.8{% elsif ghes = 3.8 %}8.1{% endif %} and later, you{% elsif ghes > 3.8 %}You{% endif %} can configure your instance's proxy settings to exclude unregistered TLDs that aren't specified in the [list of TLDs](https://data.iana.org/TLD/tlds-alpha-by-domain.txt) on the IANA website.
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 1. Enter the following command, replacing COMMA-SEPARATED-TLD-LIST with a comma-separated list of TLDs.

content/admin/configuration/configuring-your-enterprise/command-line-utilities.md

@@ -299,10 +299,10 @@ ghe-saml-mapping-csv -d
 
 {% ifversion ghes < 3.9 %}
 
-After output completes, the utility displays the path to the file. The default path for output depends on the patch release of {% data variables.product.product_name %} {% ifversion ghes = 3.5 %}3.5{% elsif ghes = 3.6 %}3.6{% elsif ghes = 3.7%}3.7{% endif %} your instance is running.
+After output completes, the utility displays the path to the file. The default path for output depends on the patch release of {% data variables.product.product_name %} {% ifversion ghes = 3.6 %}3.6{% elsif ghes = 3.7%}3.7{% endif %} your instance is running.
 
-- In version 3.{% ifversion ghes = 3.5 %}5.14{% elsif ghes = 3.6 %}6.10{% elsif ghes = 3.7%}7.7{% elsif ghes = 3.8 %}8.0{% endif %}{% ifversion ghes < 3.8 %} and earlier{% endif %}, the utility writes the file to `/tmp`.
+- In version 3.{% ifversion ghes = 3.6 %}6.10{% elsif ghes = 3.7%}7.7{% elsif ghes = 3.8 %}8.0{% endif %}{% ifversion ghes < 3.8 %} and earlier{% endif %}, the utility writes the file to `/tmp`.
-- In version 3.{% ifversion ghes = 3.5 %}5.15{% elsif ghes = 3.6 %}6.11{% elsif ghes = 3.7%}7.8{% elsif ghes = 3.8 %}8.1{% endif %} and later,
+- In version 3.{% ifversion ghes = 3.6 %}6.11{% elsif ghes = 3.7%}7.8{% elsif ghes = 3.8 %}8.1{% endif %} and later,
 
 {%- elsif ghes > 3.8 %}By default,{% endif %} the utility writes the file to `/data/user/tmp`.
 
@@ -1042,7 +1042,7 @@ git-import-rewrite
 
 ### ghe-find-insecure-git-operations
 
-This utility searches your instance's logs and identifies Git operations over SSH that use insecure algorithms or hash functions, including DSA, RSA-SHA-1, HMAC-SHA-1, and CBC ciphers. You can use the output to support each client's transition to a more secure SSH connection. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes < 3.6 %}.{% elsif ghes > 3.5 %} and "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."{% endif %}
+This utility searches your instance's logs and identifies Git operations over SSH that use insecure algorithms or hash functions, including DSA, RSA-SHA-1, HMAC-SHA-1, and CBC ciphers. You can use the output to support each client's transition to a more secure SSH connection. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes > 3.5 %} and "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."{% endif %}
 
 ```shell
 ghe-find-insecure-git-operations

content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md

@@ -20,13 +20,6 @@ shortTitle: Manage GitHub Mobile
 
 You can allow or disallow people from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.location.product_location %} and access your instance's data. By default, {% data variables.product.prodname_mobile %} is enabled for people who use {% data variables.location.product_location %}.
 
-{% ifversion ghes < 3.6 %}
-{% note %}
-
-**Note:** If you upgrade to {% data variables.product.prodname_ghe_server %} 3.4.0 or later and have not previously disabled or enabled {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_mobile %} will be enabled by default. If you previously disabled or enabled {% data variables.product.prodname_mobile %} for your instance, your preference will be preserved upon upgrade. For more information about upgrading your instance, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
-
-{% endnote %}
-{% endif %}
 
 ## Enabling or disabling {% data variables.product.prodname_mobile %}
 

content/admin/enterprise-management/caching-repositories/about-repository-caching.md

@@ -8,8 +8,6 @@ topics:
   - Enterprise
 ---
 
-{% data reusables.enterprise.repository-caching-release-phase %}
-
 If you have teams and CI farms located around the world, you may experience reduced performance on your primary {% data variables.product.prodname_ghe_server %} instance. While active geo-replicas can improve the performance of read requests, this comes at the cost of limiting write throughput. To reduce load on your primary instance and improve write throughput performance, you can configure a repository cache, an asynchronous read-only mirror of repositories located near these geographically-distributed clients.
 
 A repository cache eliminates the need for {% data variables.product.product_name %} to transmit the same Git data over a long-haul network link multiple times to serve multiple clients, by serving your repository data close to CI farms and distributed teams. For instance, if your primary instance is in North America and you also have a large presence in Asia, you will benefit from setting up the repository cache in Asia for use by CI runners there.

content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md

@@ -8,8 +8,6 @@ topics:
   - Enterprise
 ---
 
-{% data reusables.enterprise.repository-caching-release-phase %}
-
 ## About configuration for repository caching
 
 {% data reusables.enterprise.repository-caching-config-summary %} Then, you can set data location policies that govern which repository networks are replicated to the repository cache.
@@ -56,20 +54,6 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins
       ghe-repl-setup -a PRIMARY-IP
       ```
 
-{% ifversion ghes < 3.6 %}
-1. If you haven't already, set the datacenter name on the primary and any replica appliances, replacing DC-NAME with a datacenter name.
-
-   ```
-   ghe-repl-node --datacenter DC-NAME
-   ```
- 
-1. Set a `cache-location` for the repository cache, replacing CACHE-LOCATION with an alphanumeric identifier, such as the region where the cache is deployed. Also set a datacenter name for this cache; new caches will attempt to seed from another cache in the same datacenter.
-
-   ```shell
-   ghe-repl-node --cache CACHE-LOCATION --datacenter REPLICA-DC-NAME
-   ```
-
-{% else %}
 1. To configure the repository cache, use the `ghe-repl-node` command and include the necessary parameters.
     - Set a `cache-location` for the repository cache, replacing _CACHE-LOCATION_ with an alphanumeric identifier, such as the region where the cache is deployed.  The _CACHE-LOCATION_ value must not be any of the subdomains reserved for use with subdomain isolation, such as `assets` or `media`.  For a list of reserved names, see "[AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation#about-subdomain-isolation)."
     - Set a `cache-domain` for the repository cache, replacing _EXTERNAL-CACHE-DOMAIN_ with the hostname Git clients will use to access the repository cache. If you do not specify a `cache-domain`, {% data variables.product.product_name %} will prepend the _CACHE-LOCATION_ value as a subdomain to the hostname configured for your instance. For more information, see "[AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-a-hostname)."
@@ -85,8 +69,6 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins
     ghe-repl-node --cache CACHE-LOCATION --cache-domain EXTERNAL-CACHE-DOMAIN --datacenter REPLICA-DC-NAME
     ```
 
-{% endif %}
-
 {% data reusables.enterprise_installation.replication-command %}
 {% data reusables.enterprise_installation.verify-replication-channel %}
 1. To enable replication of repository networks to the repository cache, set a data location policy. For more information, see "[Data location policies](#data-location-policies)."

content/admin/enterprise-management/caching-repositories/index.md

@@ -9,5 +9,3 @@ children:
   - /about-repository-caching
   - /configuring-a-repository-cache
 ---
-
-{% data reusables.enterprise.repository-caching-release-phase %}

content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md

@@ -272,12 +272,12 @@ To upgrade an instance that comprises multiple nodes using an upgrade package, y
 
    {% endnote %}
 
-   {%- ifversion ghes = 3.5 or ghes = 3.6 %}
+   {%- ifversion ghes = 3.6 %}
 
    - If you have upgraded each node to {% data variables.product.product_name %} 3.6.0 or later and started replication, but `git replication is behind the primary` continues to appear after 45 minutes, contact {% data variables.contact.enterprise_support %}. For more information, see "[AUTOTITLE](/support/contacting-github-support)."
    {%- endif %}
 
-   - {% ifversion ghes = 3.5 or ghes = 3.6 %}Otherwise, if{% else %}If{% endif %} `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. For more information, see "[AUTOTITLE](/support/contacting-github-support)."
+   - {% ifversion ghes = 3.6 %}Otherwise, if{% else %}If{% endif %} `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. For more information, see "[AUTOTITLE](/support/contacting-github-support)."
 {% data reusables.enterprise_installation.multiple-node-repeat-upgrade-process %}
 1. After you have upgraded the last replica node and the resync is complete, disable maintenance mode so users can use {% data variables.location.product_location %}.
 

content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md

@@ -31,38 +31,11 @@ This article explains how site administrators can configure {% data variables.pr
 
 ## Review hardware requirements
 
-{%- ifversion ghes < 3.6 %}
-
-The CPU and memory resources available to {% data variables.location.product_location %} determine the number of jobs that can be run concurrently without performance loss. {% data reusables.actions.minimum-hardware %}
-
-The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations:
-
-{% endif %}
-
-{%- ifversion ghes > 3.5 %}
 
 The CPU and memory resources available to {% data variables.location.product_location %} determine the number of runners that can be configured without performance loss. {% data reusables.actions.minimum-hardware %}
 
 The peak quantity of connected runners without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated performance targets for GitHub Enterprise Server on a range of CPU and memory configurations.
 
-{% endif %}
-
-{%- ifversion ghes = 3.5 %}
-
-{% data reusables.actions.hardware-requirements-3.5 %}
-
-{% data variables.product.company_short %} measured maximum concurrency using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
-
-{% note %}
-
-**Note:** Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}.
-
-{% endnote %}
-
-{%- endif %}
-
-{%- ifversion ghes > 3.5 %}
-
 | vCPUs | Memory | Maximum Connected Runners |
 | :---| :--- | :--- |
 | 8   | 64 GB  | 740  runners |
@@ -80,7 +53,6 @@ The peak quantity of connected runners without performance loss depends on such
 
 - Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}.
 {% endnote %}
-{%- endif %}
 
 If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance)."
 

content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md

@@ -62,11 +62,6 @@ After you configure the application for {% data variables.product.product_name %
 
 {% endif %}
 
-{% ifversion ghes < 3.6 %}
-
-Your IdP does not communicate with {% data variables.product.product_name %} automatically when you assign or unassign the application. {% data variables.product.product_name %} creates a user account using SAML Just-in-Time (JIT) provisioning the first time someone navigates to {% data variables.product.product_name %} and signs in by authenticating through your IdP. You may need to manually notify users when you grant access to {% data variables.product.product_name %}.
-
-{% endif %}
 
 {% ifversion ghes %}
 

content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md

@@ -287,13 +287,13 @@ If you have [enabled private mode](/admin/configuration/configuring-your-enterpr
 
 Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. When you or a repository administrator enable this access setting for a repository, unauthenticated Git operations (and anyone with network access to {% data variables.product.product_name %}) will have read access to the repository without authentication.
 
-Anonymous Git read access is disabled by default.{% ifversion ghes = 3.5 or ghes = 3.6 or ghes = 3.7 %} When you upgrade to {% data variables.product.product_name %} 3.6 or later, anonymous Git read access is automatically disabled at the application level, and `git://` connections on port 9418 will return the following error.
+Anonymous Git read access is disabled by default.{% ifversion ghes = 3.6 or ghes = 3.7 %} When you upgrade to {% data variables.product.product_name %} 3.6 or later, anonymous Git read access is automatically disabled at the application level, and `git://` connections on port 9418 will return the following error.
 
 ```
 The unauthenticated git protocol on port 9418 is no longer supported.
 ```
 
-{% ifversion ghes > 3.5 %}
+{% ifversion ghes %}
 
 If you wish to support the unathenticated Git protocol in your environment, you must manually re-enable the feature. Run the following commands after your upgrade:
 

content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md

@@ -44,7 +44,7 @@ You can also export membership information for your enterprise. For more informa
 
 You can view all the current enterprise owners{% ifversion ghec %} and billing managers{% endif %} for your enterprise.{% ifversion enterprise-membership-view-improvements %} You can see useful information about each administrator{% ifversion ghec %} and filter the list by role{% endif %}.{% endif %} You can find a specific person by searching for their username or display name.
 
-{% ifversion ghes > 3.5 %}
+{% ifversion ghes %}
 Enterprise owners whose accounts are suspended are included in the list of enterprise administrators, and are identified as suspended. You should consider demoting any suspended owners you see. For more information, see "[AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator#demoting-a-site-administrator-from-the-enterprise-settings)."
 {% endif %}
 

content/code-security/code-scanning/troubleshooting-code-scanning/not-recognized.md

@@ -1,6 +1,6 @@
 ---
 title: 'Error: "is not a .ql file, .qls file, a directory, or a query pack specification"'
-shortTitle: 'Not recognized'
+shortTitle: Not recognized
 intro: '{% data variables.product.prodname_codeql %} was unable to locate one of the queries or sets of queries that are specified for analysis.'
 allowTitleToDifferFromFilename: true
 product: '{% data reusables.gated-features.code-scanning %}'
@@ -18,4 +18,4 @@ You will see `Error: "is not a .ql file, .qls file, a directory, or a query pack
 - There is a typo in the workflow.
 - A resource the workflow refers to by path was renamed, deleted, or moved to a new location.
 
-After verifying the location of the resource, you can update the workflow to specify the correct location. {% ifversion ghes < 3.6 or ghae < 3.6 %}If you run additional queries in Go analysis, you may have been affected by the relocation of the source files. For more information, see [Relocation announcement: `github/codeql-go` moving into `github/codeql`](https://github.com/github/codeql-go/issues/741) in the github/codeql-go repository.{% endif %}
+After verifying the location of the resource, you can update the workflow to specify the correct location. {% ifversion ghae < 3.6 %}If you run additional queries in Go analysis, you may have been affected by the relocation of the source files. For more information, see [Relocation announcement: `github/codeql-go` moving into `github/codeql`](https://github.com/github/codeql-go/issues/741) in the github/codeql-go repository.{% endif %}

content/code-security/codeql-cli/using-the-codeql-cli/getting-started-with-the-codeql-cli.md

@@ -158,7 +158,7 @@ Rename this folder `codeql-repo` to avoid conflicting with the {% data variables
 clone and rename the repository in a single step by running
 `git clone git@github.com:github/codeql.git codeql-repo` in the `codeql-home` folder.
 
-{% ifversion ghes < 3.6 or ghae < 3.6 %}
+{% ifversion ghae < 3.6 %}
 {% note %}
 
 **Note:** The {% data variables.product.prodname_codeql %} libraries and queries for Go analysis used to live in a separate [{% data variables.product.prodname_codeql %} for Go repository](https://github.com/github/codeql-go/). These have been moved to the `github/codeql` repository. It is no longer necessary to clone the `github/codeql-go` into a separate `codeql-home/codeql-go` folder.

content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md

@@ -60,8 +60,8 @@ The search bar also allows for full text searching of alerts and related securit
 {% endif %}
 
 {% ifversion dependabot-bulk-alerts %}
-![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab.](/assets/images/help/graphs/dependabot-alerts-filters-checkbox.png){% elsif ghes = 3.5 %}
+![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab.](/assets/images/help/graphs/dependabot-alerts-filters-checkbox.png)
-You can select a filter in a dropdown menu at the top of the list, then click the filter that you would like to apply.{% endif %}
+{% endif %}
 
 {% ifversion dependabot-alerts-development-label %}
 
@@ -214,7 +214,6 @@ You can view all open alerts, and you can reopen alerts that have been previousl
 1. Click the alert that you would like to view or update.
 1. Optionally, if the alert was dismissed and you wish to reopen it, click **Reopen**. Alerts that have already been fixed cannot be reopened.
 
-   {% indented_data_reference reusables.enterprise.3-5-missing-feature spaces=3 %}
    ![Screenshot showing a closed {% data variables.product.prodname_dependabot %} alert. A button, titled "Reopen", is highlighted in a dark orange outline.](/assets/images/help/repository/reopen-dismissed-alert.png)
 
 {% endif %}

content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md

@@ -38,7 +38,7 @@ Any options that also affect security updates are used the next time a security
 
 {% endnote %}
 
-The _dependabot.yml_ file has two mandatory top-level keys: `version`, and `updates`. You can, optionally, include a top-level `registries` key{% ifversion ghes = 3.5 %} and/or a `enable-beta-ecosystems` key{% endif %}. The file must start with `version: 2`.
+The _dependabot.yml_ file has two mandatory top-level keys: `version`, and `updates`. You can, optionally, include a top-level `registries` key. The file must start with `version: 2`.
 
 ## Configuration options for the _dependabot.yml_ file
 
@@ -1292,7 +1292,7 @@ There are currently no ecosystems in beta.
 
 version: 2
 enable-beta-ecosystems: true
-updates:{% ifversion fpt or ghec or ghes > 3.5 %}
+updates:{% ifversion fpt or ghec or ghes %}
   - package-ecosystem: "beta-ecosystem"{% else %}
   - package-ecosystem: "pub"{% endif %}
     directory: "/"

content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md

@@ -159,7 +159,7 @@ If you confirm a secret is real and that you intend to fix it later, you should
 
 {% data reusables.secret-scanning.push-protection-multiple-branch-note %}
 
-{% ifversion ghes < 3.6 or ghae < 3.6 %}
+{% ifversion ghae < 3.6 %}
 
 {% tip %}
 

content/code-security/secret-scanning/secret-scanning-patterns.md

@@ -106,7 +106,7 @@ This table lists the secrets supported by {% data variables.product.prodname_sec
 {% endif %}
 
 <!-- GHES 3.5 to GHES 3.8 table -->
-{% ifversion ghes = 3.5 or ghes = 3.6 or ghes = 3.7 or ghes = 3.8 %}
+{% ifversion ghes = 3.6 or ghes = 3.7 or ghes = 3.8 %}
 
 | Provider | Token | {% data variables.product.prodname_secret_scanning_caps %} alert | Push protection |
 |----|:----|:----:|:----:|

content/code-security/security-overview/about-security-overview.md

@@ -116,7 +116,7 @@ At the team level, security overview displays repository-specific security infor
 
 If you are an owner or security manager for an organization, you can see data for all the repositories in the organization in all views.{% ifversion security-overview-org-risk-coverage-enterprise %} You can see the data in the organization-level security overview, or see data for all organizations where you are an owner or security manager in the enterprise-level security overview.{% endif %}
 
-{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %}If you are an enterprise owner, you will need to join an organization as an organization owner to view data for the organization's repositories in either the organization-level or enterprise-level overview. For more information, see "[AUTOTITLE](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
+{% ifversion ghec or ghes or ghae > 3.5 %}If you are an enterprise owner, you will need to join an organization as an organization owner to view data for the organization's repositories in either the organization-level or enterprise-level overview. For more information, see "[AUTOTITLE](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
 
 If you are an organization member, you can view security overview for the organization and see data for repositories where you have access.{% ifversion security-overview-org-risk-coverage-enterprise %} You can view this data in the organization-level overview, but you cannot access the enterprise-level overview.{% endif %}
 

content/code-security/security-overview/filtering-alerts-in-security-overview.md

@@ -156,7 +156,7 @@ You can filter the view to show {% data variables.product.prodname_dependabot_al
 
 | Qualifier | Description |
 | -------- | -------- |
-{% ifversion dependabot-alerts-vulnerable-calls or ghes > 3.5 or ghae > 3.5 -%}
+{% ifversion dependabot-alerts-vulnerable-calls or ghes or ghae -%}
 |`has:patch`|Displays {% data variables.product.prodname_dependabot %} alerts for vulnerabilities where a secure version is already available.|
 |`has:vulnerable-calls`|Displays {% data variables.product.prodname_dependabot %} alerts where at least one call from the repository to a vulnerable function is detected. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#about-the-detection-of-calls-to-vulnerable-functions)."|
 {% endif -%}

content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md

@@ -38,8 +38,7 @@ You can secure the code you depend on by creating a vulnerability management pro
 1. Create an inventory of your dependencies.
 
 1. Know when there is a security vulnerability in a dependency.
-{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+1. Enforce dependency reviews on your pull requests.
-1. Enforce dependency reviews on your pull requests.{% endif %}
 
 1. Assess the impact of that vulnerability on your code and decide what action to take.
 
@@ -50,7 +49,7 @@ As a first step, you want to make a complete inventory of your dependencies. The
 ### Automatic detection of vulnerabilities in dependencies
 
 {% data variables.product.prodname_dependabot %} can help you by monitoring your dependencies and notifying you when they contain a known vulnerability. {% ifversion fpt or ghec or ghes %}You can even enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests that update the dependency to a secure version.{% endif %} For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"{% ifversion fpt or ghec or ghes %} and "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates)"{% endif %}.
-{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+{% ifversion fpt or ghec or ghes or ghae > 3.5 %}
 
 ### Automatic detection of vulnerabilities in pull requests
 

content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md

@@ -44,7 +44,7 @@ For more information on supply chain features available on {% data variables.pro
 The dependency review feature becomes available when you enable the dependency graph. For more information, see "{% ifversion ghec %}[Enabling the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph){% elsif ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% endif %}."
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+{% ifversion fpt or ghec or ghes or ghae > 3.5 %}
 
 ## Dependency review enforcement
 

content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md

@@ -104,11 +104,7 @@ The recommended formats explicitly define which versions are used for all direct
 
 - If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
 
-{% ifversion ghes = 3.5 %}
+{% ifversion github-actions-in-dependency-graph %}
-
-- Support for {% data variables.product.prodname_actions %} workflows is available from GitHub Enterprise Server 3.5.4 onward. The feature is not available in 3.5.0, 3.5.1, 3.5.2, and 3.5.3. For information about determining the version of {% data variables.product.product_name %} you're using, see "[AUTOTITLE](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
-
-{% endif %}{% ifversion github-actions-in-dependency-graph %}
 - {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs.<job_id>.uses` will be parsed as dependencies. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions)."
 
 - {% data variables.product.prodname_actions %} workflow dependencies are displayed in the dependency graph for informational purposes. Dependabot alerts are not currently supported for {% data variables.product.prodname_actions %} workflows.

content/discussions/managing-discussions-for-your-community/moderating-discussions.md

@@ -1,6 +1,6 @@
 ---
 title: Moderating discussions
-intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.'
+intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes %} organization''s contribution guidelines{% endif %}.'
 permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
 versions:
   feature: discussions

content/discussions/quickstart.md

@@ -16,7 +16,7 @@ Discussions give a space for more collaborative conversations by connecting and
 
 ## Enabling {% data variables.product.prodname_discussions %} on your repository
 
-Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public{% ifversion ghes > 3.5 %}, internal{% endif %} and private repositories. The visibility of a discussion is inherited from the repository the discussion is created in.
+Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public{% ifversion ghes %}, internal{% endif %} and private repositories. The visibility of a discussion is inherited from the repository the discussion is created in.
 
 When you first enable {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post.
 

content/get-started/quickstart/contributing-to-projects.md

@@ -30,7 +30,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
 1. In the top-right corner of the page, click **Fork**.
 
    ![Screenshot of the main page of repository. A button, labeled with a fork icon and "Fork 59.3k," is outlined in dark orange.](/assets/images/help/repository/fork_button.png)
-{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+{%- ifversion fpt or ghec or ghes or ghae > 3.5 %}
 1. Under "Owner," select the dropdown menu and click an owner for the forked repository.
 1. By default, forks are named the same as their upstream repositories. Optionally, to further distinguish your fork, in the "Repository name" field, type a name.
 1. Optionally, in the "Description" field, type a description of your fork.

content/get-started/quickstart/fork-a-repo.md

@@ -59,7 +59,7 @@ You might fork a project to propose changes to the upstream repository. In this
 1. In the top-right corner of the page, click **Fork**.
 
    ![Screenshot of the main page of repository. A button, labeled with a fork icon and "Fork 59.3k," is outlined in dark orange.](/assets/images/help/repository/fork_button.png)
-{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+{%- ifversion fpt or ghec or ghes or ghae > 3.5 %}
 1. Under "Owner," select the dropdown menu and click an owner for the forked repository.
 1. By default, forks are named the same as their upstream repositories. Optionally, to further distinguish your fork, in the "Repository name" field, type a name.
 1. Optionally, in the "Description" field, type a description of your fork.

content/get-started/using-github/keyboard-shortcuts.md

@@ -105,7 +105,7 @@ If you view a code file in a repository using the **Code** view and click on any
 |<kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | Inserts Markdown formatting for bolding text
 |<kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | Inserts Markdown formatting for italicizing text
 |<kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux) | Inserts Markdown formatting for code or a command within a line
-|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link{% ifversion fpt or ghae > 3.5 or ghes > 3.5 or ghec %}
+|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link{% ifversion fpt or ghae > 3.5 or ghes or ghec %}
 |<kbd>Command</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>V</kbd> (Windows/Linux) | Creates a Markdown link when applied over highlighted text{% endif %}
 |<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs
 |<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text

content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md

@@ -120,7 +120,7 @@ Here are the currently supported color models.
 
 You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. You can also use the keyboard shortcut <kbd>Command</kbd>+<kbd>K</kbd> to create a link. When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.
 
-{% ifversion fpt or ghae > 3.5 or ghes > 3.5 or ghec %} You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut <kbd>Command</kbd>+<kbd>V</kbd>. If you'd like to replace the text with the link, use the keyboard shortcut <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd>.{% endif %}
+You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut <kbd>Command</kbd>+<kbd>V</kbd>. If you'd like to replace the text with the link, use the keyboard shortcut <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd>.
 
 `This site was built using [GitHub Pages](https://pages.github.com/).`
 

content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md

@@ -83,7 +83,7 @@ If the branch you want to delete is associated with an open pull request, you mu
 1. Next to the branch that you want to delete, click {% octicon "trash" aria-label="The trash icon" %} .
 
    ![Screenshot of a branch in the branch list. A trash icon is highlighted with an orange outline.](/assets/images/help/branches/branches-delete.png)
-{%- ifversion fpt or ghes > 3.5 or ghae > 3.5 or ghec %}
+{%- ifversion fpt or ghes or ghae > 3.5 or ghec %}
 1. If the branch is associated with at least one open pull request, deleting the branch will close the pull requests. Read the warning, then click **Delete**.
 {%- endif %}
 

content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md

@@ -32,7 +32,7 @@ shortTitle: Review dependency changes
 
 Dependency review allows you to "shift left". You can use the provided predictive information to catch vulnerable dependencies before they hit production. For more information, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
 
-{% ifversion fpt or ghec or ghes > 3.5 %}
+{% ifversion fpt or ghec or ghes %}
 
 You can use the {% data variables.dependency-review.action_name %} to help enforce dependency reviews on pull requests in your repository. {% data reusables.dependency-review.dependency-review-action-overview %}
 

content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md

@@ -14,7 +14,7 @@ shortTitle: Configure commit merging
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow merge commits**. This allows contributors to merge a pull request with a full history of commits.
+1. Under "Pull Requests", select **Allow merge commits**. This allows contributors to merge a pull request with a full history of commits.
 {% ifversion default-merge-squash-commit-message %}
 1. Optionally, under **Allow merge commits**, select the dropdown menu, then click the format of the commit message presented to contributors when merging.
 

content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md

@@ -18,6 +18,6 @@ shortTitle: Configure commit rebasing
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow rebase merging**. This allows contributors to merge a pull request by rebasing their individual commits onto the base branch.
+1. Under "Pull Requests", select **Allow rebase merging**. This allows contributors to merge a pull request by rebasing their individual commits onto the base branch.
 
 If you also select another merge method, collaborators will be able to choose the type of merge commit when merging a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}

content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md

@@ -20,7 +20,7 @@ shortTitle: Configure commit squashing
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. The default commit message presented to contributors when merging is the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. {% ifversion ghes = 3.6 %} To always use the title of the pull request regardless of the number of commits in the pull request select **Default to PR title for squash merge commits**.{% endif %}
+1. Under "Pull Requests", select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. The default commit message presented to contributors when merging is the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. {% ifversion ghes = 3.6 %} To always use the title of the pull request regardless of the number of commits in the pull request select **Default to PR title for squash merge commits**.{% endif %}
 {% ifversion default-merge-squash-commit-message %}
 1. Optionally, under **Allow squash merging**, select the dropdown menu, then click the format of the default squash commit message presented to contributors when merging.
 

content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md

@@ -16,8 +16,6 @@ permissions: People with maintainer permissions can enable or disable the settin
 
 If you enable the setting to always suggest updating pull request branches in your repository, people with write permissions will always have the ability, on the pull request page, to update a pull request's head branch when it's not up to date with the base branch. When not enabled, the ability to update is only available when the base branch requires branches to be up to date before merging and the branch is not up to date. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
 
-{% data reusables.enterprise.3-5-missing-feature %}
-
 ## Managing suggestions to update a pull request branch
 
 {% data reusables.repositories.navigate-to-repo %}

content/repositories/releasing-projects-on-github/about-releases.md

@@ -29,7 +29,7 @@ Anyone with read access to a repository can view and compare releases, but only
 
 You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[AUTOTITLE](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
 
-{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.6 %}
+{% ifversion fpt or ghec or ghes or ghae > 3.6 %}
 When viewing the details for a release, the creation date for each release asset is shown next to the release asset.
 {% endif %}
 

content/rest/dependency-graph/index.md

@@ -1,11 +1,9 @@
 ---
 title: Dependency Graph
-intro: >-
+intro: Use the REST API to view dependency changes and their security impact on your repository.
-  Use the REST API to view dependency changes and their security impact on your
-  repository.
 versions:
   fpt: '*'
-  ghes: '>=3.6'
+  ghes: '*'
   ghec: '*'
 topics:
   - API

content/rest/rate-limit/rate-limit.md

@@ -29,7 +29,7 @@ The REST API for searching items has a custom rate limit that is separate from t
 
 - The `integration_manifest` object provides your rate limit status for the `POST /app-manifests/{code}/conversions` operation. For more information, see "[AUTOTITLE](/apps/creating-github-apps/setting-up-a-github-app/creating-a-github-app-from-a-manifest#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)."
 
-{% ifversion fpt or ghec or ghes > 3.5 %}* The `dependency_snapshots` object provides your rate limit status for submitting snapshots to the dependency graph. For more information, see "[AUTOTITLE](/rest/dependency-graph)."{% endif %}
+{% ifversion fpt or ghec or ghes %}* The `dependency_snapshots` object provides your rate limit status for submitting snapshots to the dependency graph. For more information, see "[AUTOTITLE](/rest/dependency-graph)."{% endif %}
 
 - The `code_scanning_upload` object provides your rate limit status for uploading SARIF results to code scanning. For more information, see "[AUTOTITLE](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)."
 

content/rest/teams/external-groups.md

@@ -1,9 +1,6 @@
 ---
 title: External groups
-intro: >-
+intro: Use the REST API to view the external identity provider groups that are available to your organization and manage the connection between external groups and teams in your organization.
-  Use the REST API to view the external identity provider groups that are
-  available to your organization and manage the connection between external
-  groups and teams in your organization.
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
   ghae: '*'
   ghec: '*'

data/reusables/actions/more-resources-for-ghes.md

@@ -1,8 +1,3 @@
 If you plan to enable {% data variables.product.prodname_actions %} for the users of your instance, more resources are required. 
-{%- ifversion ghes = 3.5 %}
-
-{% data reusables.actions.hardware-requirements-3.5 %}
-
-{%- endif %}
 
 For more information about these requirements, see "[AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."

data/reusables/dependabot/dependabot-alerts-filters.md

@@ -2,8 +2,8 @@ You can sort and filter {% data variables.product.prodname_dependabot_alerts %}
 
 | Option | Description | Example |
 |:---|:---|:---|
-| `ecosystem` | Displays alerts for the selected ecosystem | Use `ecosystem:npm` to show {% data variables.product.prodname_dependabot_alerts %} for npm |{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+| `ecosystem` | Displays alerts for the selected ecosystem | Use `ecosystem:npm` to show {% data variables.product.prodname_dependabot_alerts %} for npm |
-| `has` | Displays alerts meeting the selected filter criteria | Use `has:patch` to show alerts related to advisories that have a patch{% ifversion dependabot-alerts-vulnerable-calls %}</br>Use `has:vulnerable-calls` to show alerts relating to calls to vulnerable functions{% endif %} |{% endif %}
+| `has` | Displays alerts meeting the selected filter criteria | Use `has:patch` to show alerts related to advisories that have a patch{% ifversion dependabot-alerts-vulnerable-calls %}</br>Use `has:vulnerable-calls` to show alerts relating to calls to vulnerable functions |{% endif %}
 | `is` | Displays alerts based on their state | Use `is:open` to show open alerts |
 | `manifest` | Displays alerts for the selected manifest | Use `manifest:webwolf/pom.xml` to show alerts on the pom.xml file of the webwolf application |
 | `package` | Displays alerts for the selected package | Use `package:django` to show alerts for django |

data/reusables/dependabot/supported-package-managers.md

@@ -91,12 +91,7 @@ pnpm is supported for {% data variables.product.prodname_dependabot_version_upda
 
 #### pub
 
-{% ifversion ghes = 3.5 %}`pub` support is currently in beta. Any known limitations are subject to change. Note that {% data variables.product.prodname_dependabot %}:
+{% data variables.product.prodname_dependabot %} won't perform an update for `pub` when the version that it tries to update to is ignored, even if an earlier version is available.
-- Doesn't support updating git dependencies for `pub`.
-- Won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available.
-
-For information about configuring your _dependabot.yml_ file for `pub`, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems)."
-{%- else %}{% data variables.product.prodname_dependabot %} won't perform an update for `pub` when the version that it tries to update to is ignored, even if an earlier version is available.{% endif %}
 {% endif %}
 
 {% ifversion dependabot-yarn-v3-update %}

data/reusables/enterprise/3-5-missing-feature.md

@@ -1,11 +0,0 @@
-{% ifversion ghes = 3.5 %}
-
-{% note %}
-
-**Note**: This feature was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
-
-For more information about determining the version of {% data variables.product.product_name %} you're using, see "[AUTOTITLE](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
-
-{% endnote %}
-
-{% endif %}

data/reusables/enterprise/repository-caching-release-phase.md

@@ -1,7 +0,0 @@
-{% ifversion ghes < 3.6 %}
-{% note %}
-
-**Note:** Repository caching is currently in beta and subject to change.
-
-{% endnote %}
-{% endif %}

data/reusables/enterprise_site_admin_settings/3-7-new-subdomains.md

@@ -1,8 +1,8 @@
-{% ifversion ghes = 3.5 or ghes = 3.6 or ghes = 3.7 or ghes = 3.8 %}
+{% ifversion ghes = 3.6 or ghes = 3.7 or ghes = 3.8 %}
 
 {% note %}
 
-{%- ifversion ghes = 3.5 or ghes = 3.6 %}
+{%- ifversion ghes = 3.6 %}
 
 **Note**: The `http(s)://render.HOSTNAME` subdomain is deprecated in {% data variables.product.product_name %} 3.7 and later. After you upgrade to 3.7 or later, ensure that your TLS certificate covers the subdomains for the replacement services, `http(s)://notebooks.HOSTNAME` and `http(s)://viewscreen.HOSTNAME`.
 

data/reusables/gated-features/dependency-vulnerable-calls.md

@@ -4,7 +4,7 @@ Detection of vulnerable calls is enabled on public repositories. This analysis i
 {%- elsif ghec %}
 Detection of vulnerable calls is included in {% data variables.product.product_name %} for public repositories. To detect vulnerable calls in private repositories owned by organizations, your organization must have a license for {% data variables.product.prodname_GH_advanced_security %}.
 
-{%- elsif ghes > 3.5 %}
+{%- elsif ghes %}
 Detection of vulnerable calls is available for organization-owned repositories in {% data variables.product.product_name %}. This feature requires a license for {% data variables.product.prodname_GH_advanced_security %}.
 
 {%- elsif ghae > 3.5 %}

data/reusables/release-notes/2022-09-hotpatch-issue.md

@@ -1,4 +1,4 @@
-Hotpatch upgrades to GitHub Enterprise Server {% ifversion ghes = 3.5 %}3.5.6{% elsif ghes = 3.6 %}3.6.2{% endif %} may fail. Upgrades with the full `.pkg` are unaffected. If the upgrade fails for your instance, workaround this issue by connecting to the administrative shell (ssh) and running the following non-interactive command:
+Hotpatch upgrades to GitHub Enterprise Server {% ifversion ghes = 3.6 %}3.6.2{% endif %} may fail. Upgrades with the full `.pkg` are unaffected. If the upgrade fails for your instance, workaround this issue by connecting to the administrative shell (ssh) and running the following non-interactive command:
 
 ```
 echo "grub-pc grub-pc/install_devices_empty boolean true" | sudo debconf-set-selections

data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md

@@ -1,10 +1,10 @@
-{% ifversion ghes = 3.5 or ghes = 3.6 %}
+{% ifversion ghes = 3.6 %}
 
 In some cases, GitHub Advanced Security customers who upgrade to GitHub Enterprise Server {{ allVersions[currentVersion].currentRelease }} may notice that alerts from secret scanning are missing in the web UI and REST API. To ensure the alerts remain visible, do not skip 3.4 as you upgrade to the latest release. To plan an upgrade through 3.4, see the [Upgrade assistant](https://support.github.com/enterprise/server-upgrade).
 
 - To display the missing alerts for all repositories owned by an organization, organization owners can navigate to the organization's **Code security and analysis** settings, then click **Enable all** for secret scanning. For more information, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-existing-repositories)."
 - To display the missing alerts for an individual repository, people with admin access to the repository can disable then enable secret scanning for the repository. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)."
 
-A fix is available in the {% ifversion ghes = 3.5 %}[3.5.5](/admin/release-notes#3.5.5){% elsif ghes = 3.6 %}[3.6.1](/admin/release-notes#3.6.1){% endif %} patch release. [Updated: 2022-09-01]
+A fix is available in the {% ifversion ghes = 3.6 %}[3.6.1](/admin/release-notes#3.6.1){% endif %} patch release. [Updated: 2022-09-01]
 
 {% endif %}

data/variables/product.yml

@@ -82,7 +82,7 @@ prodname_codeql_cli: 'CodeQL CLI'
 # CodeQL usually bumps its minor version for each minor version of GHES.
 # Update this whenever a new enterprise version of CodeQL is being prepared.
 codeql_cli_ghes_recommended_version: >-
-  {% ifversion ghae < 3.5 %}2.7.6{% elsif ghes = 3.5 or ghae = 3.5 %}2.11.6{% elsif ghes < 3.10 or ghae < 3.10 %}2.12.7{% endif %}
+  {% ifversion ghae < 3.5 %}2.7.6{% elsif ghae = 3.5 %}2.11.6{% elsif ghes < 3.10 or ghae < 3.10 %}2.12.7{% endif %}
 
 # Projects v2
 prodname_projects_v2: '{% ifversion ghes = 3.8 or ghes = 3.9 %}Projects (beta){% else %}Projects{% endif %}'