docs-bot · Nov 4, 2026 · Nov 4, 2026 · Nov 4, 2026 · Nov 4, 2026 · Nov 4, 2026
diff --git a/content/actions/reference/security/oidc.md b/content/actions/reference/security/oidc.md
@@ -156,8 +156,6 @@ You can create a subject that filters for specific tag. In this example, the wor
 * Syntax: `repo:ORG-NAME/REPO-NAME:ref:refs/tags/TAG-NAME`
 * Example: `repo:octo-org/octo-repo:ref:refs/tags/demo-tag`
 
-{% ifversion fpt or ghec or ghes > 3.18 %}
-
 ### Filtering for metadata containing `:`
 
 Any `:` within the metadata values will be replaced with `%3A` in the subject claim.
@@ -167,8 +165,6 @@ You can configure a subject that includes metadata containing colons. In this ex
 * Syntax: `repo:ORG-NAME/REPO-NAME:environment:ENVIRONMENT-NAME`
 * Example: `repo:octo-org/octo-repo:environment:Production%3AV1`
 
-{% endif %}
-
 ## Immutable subject claims
 
 The OpenID Connect (OIDC) specification requires subject (`sub`) claims to be locally unique and never reassigned. Previously, the default `sub` format used only organization and repository names. If a namespace was recycled, a different owner could create the same subject value.

diff --git a/...nce/administering-your-instance-from-the-command-line/command-line-utilities.md b/...nce/administering-your-instance-from-the-command-line/command-line-utilities.md
@@ -190,8 +190,6 @@ Flag | Description
 `--error-checks-only` | Only run high severity checks that should be treated as blocking errors.
 `--warning-checks-only` | Only run low severity checks that can be treated as warnings.
 
-{% ifversion ghes > 3.18 %}
-
 ### ghe-crypto
 
 This utility is used to verify and list {% data variables.enterprise.management_console %} `github-ssl` crypto settings for TLS and SSH connections.
@@ -276,8 +274,6 @@ ghe-crypto check ssh-ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.co
 
 For more information about configuring cipher suites and cryptographic algorithms, see [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-tls-and-ssh-ciphers).
 
-{% endif %}
-
 ### ghe-console
 
 This utility opens the GitHub Rails console on your {% data variables.product.prodname_enterprise %} appliance. {% data reusables.command_line.use_with_support_only %}

diff --git a/...ng-security-for-your-enterprise/configuring-ssh-connections-to-your-instance.md b/...ng-security-for-your-enterprise/configuring-ssh-connections-to-your-instance.md
@@ -19,12 +19,8 @@ category:
 
 To accommodate the SSH clients in your environment, you can configure the types of connections that {% data variables.location.product_location %} will accept.
 
-{% ifversion ghes > 3.18 %}
-
 You can also configure the cryptographic algorithms (ciphers, MAC algorithms, key exchange algorithms, and signature types) that {% data variables.location.product_location %} uses for SSH connections. For more information, see [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-tls-and-ssh-ciphers).
 
-{% endif %}
-
 ## Configuring SSH connections with RSA keys
 
 When users perform Git operations on {% data variables.location.product_location %} via SSH over port 22, the client can authenticate with an RSA key. The client may sign the attempt using the SHA-1 hash function. In this context, the SHA-1 hash function is no longer secure. For more information, see [SHA-1](https://en.wikipedia.org/wiki/SHA-1) on Wikipedia.

diff --git a/...tings/hardening-security-for-your-enterprise/configuring-tls-and-ssh-ciphers.md b/...tings/hardening-security-for-your-enterprise/configuring-tls-and-ssh-ciphers.md
@@ -8,7 +8,7 @@ redirect_from:
   - /admin/configuration/configuring-network-settings/configuring-tls#configuring-cipher-suites-and-cryptographic-algorithms
   - /admin/configuration/hardening-security-for-your-enterprise/configuring-tls#configuring-cipher-suites-and-cryptographic-algorithms
 versions:
-  ghes: '>=3.19'
+  ghes: '*'
 contentType: how-tos
 category:
   - Secure and govern your enterprise

diff --git a/.../configuring-settings/hardening-security-for-your-enterprise/configuring-tls.md b/.../configuring-settings/hardening-security-for-your-enterprise/configuring-tls.md
@@ -119,10 +119,6 @@ To resolve these errors, you must update the Subject Alternative Names (SANs) yo
 
 1. If you configured a user message or maintenance mode, remove the message and disable maintenance mode.
 
-{% ifversion ghes > 3.18 %}
-
 ## Configuring cipher suites and cryptographic algorithms
 
 You can configure the cipher suites and cryptographic algorithms that {% data variables.product.prodname_ghe_server %} uses for TLS and SSH connections. For more information, see [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-tls-and-ssh-ciphers).
-
-{% endif %}
diff --git a/...for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/...for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -60,9 +60,7 @@ You can enforce strict controls without defining exceptions or additional config
 * **Allow all actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %}:** Any action {% ifversion actions-workflow-policy %}or reusable workflow{% endif %} can be used, regardless of who authored it or where it is defined.
 * **Allow enterprise actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %}:** Only actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} defined in a repository within the enterprise can be used. {% ifversion ghec %}Blocks all access to actions authored by {% data variables.product.prodname_dotcom %}, such as the [`actions/checkout`](https://github.com/actions/checkout) action.{% endif %}
 * {% data reusables.actions.policy-label-for-select-actions-workflows %}: Any action {% ifversion actions-workflow-policy %}or reusable workflow{% endif %} defined in a repository within the enterprise can be used, plus any action {% ifversion actions-workflow-policy %}or reusable workflow{% endif %} that matches criteria you specify.
-{%- ifversion actions-blocklist-sha-pinning %}
 * **Require actions to be pinned to a full-length commit SHA**: All actions must be pinned to a full-length commit SHA to be used. This includes actions from your enterprise and actions authored by {% data variables.product.github %}. {% ifversion actions-workflow-policy %}Reusable workflows can still be referenced by tag.{% endif %} For more information, see [AUTOTITLE](/actions/reference/security/secure-use#using-third-party-actions).
-{%- endif %}
 
 <span id="allowing-select-actions-and-reusable-workflows-to-run" ></span>
 
@@ -74,7 +72,7 @@ If you choose this option, actions {% ifversion actions-workflow-policy %}and re
 * **Allow Marketplace actions by verified creators:** Allows all {% data variables.product.prodname_marketplace %} actions created by verified creators, labeled with {% octicon "verified" aria-label="The verified badge" %}.{% ifversion ghes %}
 
    Only available if you have {% data variables.product.prodname_github_connect %} enabled and configured with {% data variables.product.prodname_actions %}. See [AUTOTITLE](/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect).{% endif %}
-* **Allow{% ifversion actions-blocklist-sha-pinning %} or block{% endif %} specified actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}:** Allows actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} that you specify. You can specify individual actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} or entire organizations and repositories.
+* **Allow or block specified actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}:** Allows actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} that you specify. You can specify individual actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} or entire organizations and repositories.
 
 When specifying actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, use the following syntax:
 
@@ -88,11 +86,9 @@ When specifying actions{% ifversion actions-workflow-policy %} and reusable work
    * To allow all actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} in repositories that start with octocat, use `*/octocat**@*`.
 * To specify multiple patterns, use `,` to separate patterns.
    * To allow all actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} from the `octocat` and `octokit` organizations, use `octocat/*, octokit/*`.
-{%- ifversion actions-blocklist-sha-pinning %}
 * To block specific patterns, use the `!` prefix.
    * To allow all actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} from the `space-org` organization, but block a specific action like `space-org/action`, use `space-org/*, !space-org/action@*`.
    * By default, only actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} specified in the list will be allowed. To allow all actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} while also blocking specific actions, use `*, !space-org/action@*`.
-{%- endif %}
 
 {% data reusables.actions.lockfile-allowed-actions-sha %}
 

diff --git a/...enforcing-policies-for-your-enterprise/managing-policies-for-code-governance.md b/...enforcing-policies-for-your-enterprise/managing-policies-for-code-governance.md
@@ -61,8 +61,6 @@ You can edit a ruleset to change parts of the ruleset, such as the name, bypass
 
 {% endif %}
 
-{% ifversion repo-rules-management %}
-
 ## Importing a ruleset
 
 You can import a ruleset from another repository, organization or enterprise using the exported JSON file from the previous section. This can be useful if you want to apply the same ruleset to multiple repositories, organizations or enterprises.
@@ -73,8 +71,6 @@ You can import a ruleset from another repository, organization or enterprise usi
 1. Open the exported JSON file.
 1. Review the imported ruleset and click **Create**.
 
-{% endif %}
-
 ## Viewing insights for rulesets
 
 You can view insights for rulesets to see how rulesets are affecting the repositories in your enterprise. {% data reusables.repositories.about-ruleset-insights %}

diff --git a/...stance/configuring-high-availability/elasticsearch-cross-cluster-replication.md b/...stance/configuring-high-availability/elasticsearch-cross-cluster-replication.md
@@ -3,7 +3,7 @@ title: Configuring Elasticsearch Cross-Cluster Replication for high availability
 shortTitle: Elasticsearch Cross-Cluster Replication
 intro: 'You can make search more resilient during maintenance, failovers, and upgrades on a high availability deployment by enabling Elasticsearch Cross-Cluster Replication (CCR).'
 versions:
-  ghes: '>=3.19'
+  ghes: '*'
 contentType: how-tos
 category:
   - Scale your instance

diff --git a/...e/monitoring-your-instance/opentelemetry-metrics/about-opentelemetry-metrics.md b/...e/monitoring-your-instance/opentelemetry-metrics/about-opentelemetry-metrics.md
@@ -11,12 +11,6 @@ category:
 
 {% data reusables.enterprise.opentelemetry-migration %}
 
-{% ifversion ghes = 3.18 %}
-
-{% data reusables.enterprise.opentelemetry-preview %}
-
-{% endif %}
-
 ## About OpenTelemetry metrics
 
 The OpenTelemetry monitoring stack is based on industry-standard observability tools and includes various components for collecting, processing, and storing metrics. This comprehensive approach provides a complete view of your system's performance and health across all components of your {% data variables.product.prodname_ghe_server %} instance.

diff --git a/...-instance/monitoring-your-instance/opentelemetry-metrics/advanced-dashboards.md b/...-instance/monitoring-your-instance/opentelemetry-metrics/advanced-dashboards.md
@@ -13,24 +13,14 @@ category:
 
 {% data reusables.enterprise.opentelemetry-migration %}
 
-{% ifversion ghes = 3.18 %}
-
-{% data reusables.enterprise.opentelemetry-preview %}
-
-{% endif %}
-
 ## Prerequisites
 
 * OpenTelemetry metrics are enabled for your {% data variables.product.prodname_ghe_server %} instance
 
 
 ## Additional dashboards
 
-{% ifversion ghes < 3.19 %}
-When OpenTelemetry metrics are enabled, you can turn on advanced Grafana dashboards with enhanced visualization and monitoring capabilities.
-{% else %}
 When OpenTelemetry metrics are enabled, you will have access to advanced Grafana dashboards with enhanced visualization and monitoring capabilities.
-{% endif %}
 
 * **Elasticsearch** - Detailed metrics for search performance, indexing operations, and cluster health
 * **Nomad** - In-depth monitoring of job scheduling, resource allocation, and service orchestration
@@ -39,25 +29,3 @@ When OpenTelemetry metrics are enabled, you will have access to advanced Grafana
 * **Process Exporter** - Detailed process-level metrics for monitoring individual service performance
 
 These dashboards provide more granular insights into your {% data variables.product.prodname_ghe_server %} instance's performance and can help with advanced troubleshooting and capacity planning.
-
-{% ifversion ghes < 3.19 %}
-## Enabling advanced dashboards
-
-### Prerequisites
-
-* SSH access to your {% data variables.product.prodname_ghe_server %} instance
-
----
-
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-1. Run the following command to enable advanced dashboards:
-
-   ```shell
-   ghe-config observability.metrics.advanced-dashboards-enabled true
-   ```
-
-{% data reusables.enterprise.apply-configuration %}
-
-After running these commands, your external Grafana instance will have access to additional pre-configured dashboards.
-{% endif %}
diff --git a/...r-instance/opentelemetry-metrics/configuring-opentelemetry-for-your-instance.md b/...r-instance/opentelemetry-metrics/configuring-opentelemetry-for-your-instance.md
@@ -11,12 +11,6 @@ category:
 
 {% data reusables.enterprise.opentelemetry-migration %}
 
-{% ifversion ghes = 3.18 %}
-
-{% data reusables.enterprise.opentelemetry-preview %}
-
-{% endif %}
-
 ## Prerequisites
 
 * {% data variables.product.prodname_ghe_server %} 3.18 or later
@@ -27,16 +21,8 @@ category:
 
 {% ifversion ghes-collectd-available %}
 
-{% ifversion ghes > 3.18 %}
-
 OpenTelemetry metrics are enabled by default for **new installations** of {% data variables.product.prodname_ghe_server %} 3.19 and later. Instances upgraded from earlier releases still have collectd metrics enabled by default. For the complete migration procedure for instances that still use collectd, including how to disable collectd, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/migration-guidance).
 
-{% else %}
-
-OpenTelemetry metrics are disabled by default. They can be enabled through the {% data variables.enterprise.management_console %} or command line.
-
-{% endif %}
-
 ### Using the {% data variables.enterprise.management_console %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}

diff --git a/...-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/index.md b/...-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/index.md
@@ -14,9 +14,3 @@ shortTitle: OpenTelemetry metrics
 ---
 
 {% data reusables.enterprise.opentelemetry-migration %}
-
-{% ifversion ghes = 3.18 %}
-
-{% data reusables.enterprise.opentelemetry-preview %}
-
-{% endif %}
diff --git a/...ance/opentelemetry-metrics/setting-up-external-monitoring-with-opentelemetry.md b/...ance/opentelemetry-metrics/setting-up-external-monitoring-with-opentelemetry.md
@@ -9,12 +9,6 @@ category:
   - Monitor and audit your enterprise
 ---
 
-{% ifversion ghes = 3.18 %}
-
-{% data reusables.enterprise.opentelemetry-preview %}
-
-{% endif %}
-
 ## External monitoring approaches
 
 External monitoring with OpenTelemetry allows you to integrate your {% data variables.product.prodname_ghe_server %} instance with existing monitoring infrastructure and tools. {% data variables.product.prodname_ghe_server %} provides two primary approaches for external monitoring:

diff --git a/content/admin/overview/establishing-a-governance-framework-for-your-enterprise.md b/content/admin/overview/establishing-a-governance-framework-for-your-enterprise.md
@@ -105,14 +105,10 @@ See [AUTOTITLE](/code-security/concepts/secret-security/push-protection).
 
 Push protection can be enabled at the organization, repository, and user account level. See [AUTOTITLE](/code-security/how-tos/secure-your-secrets/prevent-future-leaks/enable-push-protection).
 
-{% ifversion push-protected-pattern-configuration %}
-
 {% data reusables.secret-scanning.push-protected-pattern-configuration-org-enterprise-preview %}
 
 To align secret detection with internal security policies and more effectively prevent unauthorized exposure of sensitive information in your repositories, you can customize which secret patterns are included in push protection at the enterprise or organization level. See [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-enterprise-security/establish-complete-coverage/configure-additional-settings#specifying-patterns-to-include-in-push-protection-for-your-enterprise) and [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/configure-global-settings#specifying-patterns-to-include-in-push-protection).
 
-{% endif %}
-
 ## Setting up an approval process for sensitive actions
 
 You may want to set up an approval process for better control over who in your enterprise can perform sensitive actions. An approval process helps mitigate the risk of unauthorized or malicious changes, and can provide a record of who used the bypass and why, ensuring that all actions are traceable and accountable.

diff --git a/...s/creating-github-apps/about-creating-github-apps/about-creating-github-apps.md b/...s/creating-github-apps/about-creating-github-apps/about-creating-github-apps.md
@@ -51,7 +51,7 @@ To use your {% data variables.product.prodname_github_app %}, you need to instal
 
 * If your {% data variables.product.prodname_github_app %} is **private**, you can only install it on the account that owns the app.
 * If your {% data variables.product.prodname_github_app %} is **public**, other accounts can also install it.{% ifversion enterprise-apps-public-beta %}
-* If your {% data variables.product.prodname_github_app %} is owned by an **enterprise**, you can install it on {% ifversion enterprise-installed-apps %}the enterprise itself or {% endif %}any organization within that enterprise.{% endif %}{% ifversion restrictive-app-authz %} Only members of the enterprise can sign in to it.{% endif %}
+* If your {% data variables.product.prodname_github_app %} is owned by an **enterprise**, you can install it on {% ifversion enterprise-installed-apps %}the enterprise itself or {% endif %}any organization within that enterprise.{% endif %} Only members of the enterprise can sign in to it.
 
 For more information, see [AUTOTITLE](/apps/using-github-apps/installing-your-own-github-app) and [AUTOTITLE](/apps/sharing-github-apps/sharing-your-github-app).