diff --git a/content/admin/data-residency/network-details-for-ghecom.md b/content/admin/data-residency/network-details-for-ghecom.md index fa87b67f8ef3..c850517c7831 100644 --- a/content/admin/data-residency/network-details-for-ghecom.md +++ b/content/admin/data-residency/network-details-for-ghecom.md @@ -36,39 +36,34 @@ To access your enterprise on {% data variables.enterprise.data_residency_site %} These are {% data variables.product.company_short %}'s IP address ranges for enterprises hosted in the EU. -#### Ranges for egress traffic - -* 108.143.221.96/28 -* 20.61.46.32/28 -* 20.224.62.160/28 -* 51.12.252.16/28 -* 74.241.131.48/28 -* 20.240.211.176/28 - -#### Ranges for ingress traffic - -* 108.143.197.176/28 -* 20.123.213.96/28 -* 20.224.46.144/28 -* 20.240.194.240/28 -* 20.240.220.192/28 -* 20.240.211.208/28 +| Ranges for egress traffic | Ranges for ingress traffic | +|--------------------------|---------------------------| +| 108.143.221.96/28 | 108.143.197.176/28 | +| 20.61.46.32/28 | 20.123.213.96/28 | +| 20.224.62.160/28 | 20.224.46.144/28 | +| 51.12.252.16/28 | 20.240.194.240/28 | +| 74.241.131.48/28 | 20.240.220.192/28 | +| 20.240.211.176/28 | 20.240.211.208/28 | ### Australia These are {% data variables.product.company_short %}'s IP address ranges for enterprises hosted in Australia. -#### Ranges for egress traffic +| Ranges for egress traffic | Ranges for ingress traffic | +|--------------------------|---------------------------| +| 20.5.34.240/28 | 4.237.73.192/28 | +| 20.5.146.128/28 | 20.5.226.112/28 | +| 68.218.155.16/28 | 20.248.163.176/28 | -* 20.5.34.240/28 -* 20.5.146.128/28 -* 68.218.155.16/28 +### US -#### Ranges for ingress traffic +These are {% data variables.product.company_short %}'s IP address ranges for enterprises hosted in the US. -* 4.237.73.192/28 -* 20.5.226.112/28 -* 20.248.163.176/28 +| Ranges for egress traffic | Ranges for ingress traffic | +|--------------------------|---------------------------| +| 20.221.76.128/28 | 74.249.180.192/28 | +| 135.233.115.208/28 | 48.214.149.96/28 | +| 20.118.27.192/28 | 172.202.123.176/28 | ## Supported regions for Azure private networking @@ -90,6 +85,14 @@ If you use Azure private networking for {% data variables.product.company_short | arm64 | `australiaeast`, `australiacentral` | | GPU | N/A | +### Supported regions in the US + +| Runner type | Supported regions | +| ----------- | ----------------- | +| x64 | `centralus`, `eastus2`, `westus3` | +| arm64 | `centralus`, `eastus2`, `westus3` | +| GPU | `centralus`, `eastus2`, `westus3` | + ## IP ranges for {% data variables.product.prodname_importer_proper_name %} If you're running a migration to your enterprise with {% data variables.product.prodname_importer_proper_name %}, you may need to add certain ranges to an IP allow list. See [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products#configuring-ip-allow-lists-for-migrations). @@ -134,3 +137,10 @@ You must allow: * 20.5.34.240/28 * 20.5.146.128/28 * 68.218.155.16/28 + +### Required in the US + +* 130.213.245.128/28 +* 20.171.204.144/28 +* 20.171.204.176/28 +* 4.150.167.192/28 diff --git a/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md b/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md index 500867685d0d..ee281f84be65 100644 --- a/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md +++ b/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md @@ -20,7 +20,7 @@ To set up a trial, you must be signed in to a personal account. If you don't hav Set up a trial of {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 %} ->[!IMPORTANT] Your trial enterprise will be hosted in the USA. If you require {% data variables.enterprise.data_residency_short %} outside the USA, contact {% data variables.contact.contact_sales_data_residency %}. +>[!IMPORTANT] Your trial enterprise will be hosted in the US. If you require {% data variables.enterprise.data_residency_short %} in a specific region, contact {% data variables.contact.contact_sales_data_residency %}. {% data reusables.enterprise.enterprise-types %} diff --git a/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/content/repositories/creating-and-managing-repositories/transferring-a-repository.md index 81ae7f772623..d79bb212cca4 100644 --- a/content/repositories/creating-and-managing-repositories/transferring-a-repository.md +++ b/content/repositories/creating-and-managing-repositories/transferring-a-repository.md @@ -66,8 +66,7 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc ``` > [!WARNING] - > If you create a new repository or fork at the previous repository location, the redirects to the transferred repository will be deactivated. They can be reactivated by renaming or deleting the new repository or fork. - + > If you create a new repository or fork at the previous repository location, the redirects to the transferred repository will be permanently deleted. * When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository) and [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization).{% ifversion fpt or ghec %} * Sponsors who have access to the repository through a sponsorship tier may be affected. See [AUTOTITLE](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier).{% endif %} * Packages associated with the repository may be transferred, or may lose their link to the repository, depending on the registry they belong to. See [AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#about-repository-transfers). diff --git a/data/features/cluster-node-removal.yml b/data/features/cluster-node-removal.yml deleted file mode 100644 index e555c7d51fe1..000000000000 --- a/data/features/cluster-node-removal.yml +++ /dev/null @@ -1,5 +0,0 @@ -# Issue #12966 -# ghe-remove-node command line utility - -versions: - ghes: '>=3.12' diff --git a/data/features/code-scanning-task-lists.yml b/data/features/code-scanning-task-lists.yml deleted file mode 100644 index 14ba8f5e2d5b..000000000000 --- a/data/features/code-scanning-task-lists.yml +++ /dev/null @@ -1,3 +0,0 @@ -versions: - fpt: '*' - ghec: '*' diff --git a/data/features/dependabot-updates-failure-15-skip-schedule.yml b/data/features/dependabot-updates-failure-15-skip-schedule.yml deleted file mode 100644 index 035f5b648686..000000000000 --- a/data/features/dependabot-updates-failure-15-skip-schedule.yml +++ /dev/null @@ -1,5 +0,0 @@ -# Reference: Issue #13851 Dependabot version updates will skip scheduled runs after 15 failed runs. Dependabot security updates not affected. -versions: - fpt: '*' - ghec: '*' - ghes: '>= 3.13' diff --git a/data/features/dependabot-updates-reference-private-registries.yml b/data/features/dependabot-updates-reference-private-registries.yml deleted file mode 100644 index 098623cbd54e..000000000000 --- a/data/features/dependabot-updates-reference-private-registries.yml +++ /dev/null @@ -1,6 +0,0 @@ -# Reference: #13873 -# Dependabot security updates will reference private registries even if a target-branch is specified - [GA] -versions: - fpt: '*' - ghec: '*' - ghes: '> 3.12' diff --git a/data/features/dependabot-updates-v680-nuget-support.yml b/data/features/dependabot-updates-v680-nuget-support.yml deleted file mode 100644 index 2f3d403a7c08..000000000000 --- a/data/features/dependabot-updates-v680-nuget-support.yml +++ /dev/null @@ -1,5 +0,0 @@ -# Reference: #13349 - Update Dependabot YML supported NuGet version -versions: - fpt: '*' - ghec: '*' - ghes: '>3.12' diff --git a/data/features/discussions.yml b/data/features/discussions.yml deleted file mode 100644 index 66a3bb8592a4..000000000000 --- a/data/features/discussions.yml +++ /dev/null @@ -1,4 +0,0 @@ -versions: - fpt: '*' - ghec: '*' - ghes: '>=3.6' diff --git a/data/features/repo-rules-dependabot-bypass.yml b/data/features/repo-rules-dependabot-bypass.yml deleted file mode 100644 index 443be3cf2516..000000000000 --- a/data/features/repo-rules-dependabot-bypass.yml +++ /dev/null @@ -1,6 +0,0 @@ -# Reference: #13703 -# Dependabot ruleset bypass - [GA] -versions: - fpt: '*' - ghec: '*' - ghes: '>=3.13' diff --git a/data/features/secret-scanning-bypass-filter.yml b/data/features/secret-scanning-bypass-filter.yml deleted file mode 100644 index ddc3bf4729b6..000000000000 --- a/data/features/secret-scanning-bypass-filter.yml +++ /dev/null @@ -1,6 +0,0 @@ -# Reference: #12554 -# Documentation for secret scanning: filter by bypassed secrets in alert view -versions: - fpt: '*' - ghec: '*' - ghes: '>3.12' diff --git a/data/features/secret-scanning-push-protection-custom-patterns.yml b/data/features/secret-scanning-push-protection-custom-patterns.yml deleted file mode 100644 index cda8a1201cf3..000000000000 --- a/data/features/secret-scanning-push-protection-custom-patterns.yml +++ /dev/null @@ -1,7 +0,0 @@ -# Reference: #8542 -# Secret scanning: Push protection for custom patterns -# Ref 17108 Advanced Security available to Team plans -versions: - fpt: '*' - ghec: '*' - ghes: '>=3.9' diff --git a/data/features/security-overview-additional-tools.yml b/data/features/security-overview-additional-tools.yml deleted file mode 100644 index e4a8231691cc..000000000000 --- a/data/features/security-overview-additional-tools.yml +++ /dev/null @@ -1,7 +0,0 @@ -# Reference: #13509 -# Documentation for: Additional data for the overview page [Public Beta] -# Ref 17108 Advanced Security available to Team plans -versions: - fpt: '*' - ghes: '>3.12' - ghec: '*' diff --git a/data/reusables/actions/azure-vnet-supported-regions.md b/data/reusables/actions/azure-vnet-supported-regions.md index d8bd16929c70..82afe2664ec3 100644 --- a/data/reusables/actions/azure-vnet-supported-regions.md +++ b/data/reusables/actions/azure-vnet-supported-regions.md @@ -8,6 +8,7 @@ The following regions are supported on {% data variables.product.prodname_dotcom
  • AustraliaEast
  • BrazilSouth
  • CanadaCentral
    • +
  • CanadaEast
  • CentralUs
  • EastAsia
  • EastUs
    • diff --git a/data/reusables/data-residency/when-you-adopt-data-residency.md b/data/reusables/data-residency/when-you-adopt-data-residency.md index 4a577a273a1e..72ca1d801f9c 100644 --- a/data/reusables/data-residency/when-you-adopt-data-residency.md +++ b/data/reusables/data-residency/when-you-adopt-data-residency.md @@ -1,8 +1,9 @@ -When you adopt {% data variables.enterprise.data_residency %}, you can choose where your company's code and data are stored. Your enterprise will be hosted on a dedicated subdomain of {% data variables.enterprise.data_residency_site %}. +When you adopt {% data variables.enterprise.data_residency %}, you can choose where your company's code and data are stored. Your enterprise will be hosted on a dedicated subdomain of {% data variables.enterprise.data_residency_site %}. Data residency makes it easy to separate open source and enterprise work, and helps you meet specific data residency compliance requirements. The available regions are: -* The EU +* EU * Australia +* US In the future, {% data variables.product.github %} plans to offer {% data variables.enterprise.data_residency_short %} in more regions. diff --git a/data/reusables/enterprise_clustering/failover-blocks-ips.md b/data/reusables/enterprise_clustering/failover-blocks-ips.md deleted file mode 100644 index db2202dedb28..000000000000 --- a/data/reusables/enterprise_clustering/failover-blocks-ips.md +++ /dev/null @@ -1 +0,0 @@ -As a result of this fix, `ghe-cluster-failover` identifies IPs to block from the old primary cluster and writes them to `/data/user/common/cluster-ip-blocklist`. After the failover completes, the command runs `ghe-cluster-block-ips` to block the IPs on the new active cluster. diff --git a/data/variables/product.yml b/data/variables/product.yml index 1fa15998219f..3edbd67a4956 100644 --- a/data/variables/product.yml +++ b/data/variables/product.yml @@ -202,8 +202,8 @@ prodname_code_security: '{% ifversion ghas-products %}Code Security{% else %}Adv prodname_secret_protection: '{% ifversion ghas-products %}Secret Protection{% else %}Advanced Security{% endif %}' prodname_cs_or_sp: '{% ifversion ghas-products %}Secret Protection or Code Security{% else %}Advanced Security{% endif %}' prodname_cs_and_sp: '{% ifversion ghas-products %}Secret Protection and Code Security{% else %}Advanced Security{% endif %}' -UI_advanced_security: '{% ifversion ghas-products %}{% data variables.product.prodname_AS %}{% elsif code-security-wording-only %}Code security{% else %}Code security and analysis{% endif %}' -UI_advanced_security_ent: '{% ifversion ghas-products %}{% data variables.product.prodname_AS %}{% elsif code-security-wording-only-enterprise %}Code security{% else %}Code security and analysis{% endif %}' +UI_advanced_security: '{% ifversion ghas-products %}{% data variables.product.prodname_AS %}{% elsif ghes > 3.15 %}Code security{% else %}Code security and analysis{% endif %}' +UI_advanced_security_ent: '{% ifversion ghas-products %}{% data variables.product.prodname_AS %}{% elsif ghes > 3.14 %}Code security{% else %}Code security and analysis{% endif %}' UI_code_security_scanning: '{% ifversion ghas-products %}Code Security{% else %}Code scanning{% endif %}' UI_secret_protection_scanning: '{% ifversion ghas-products %}Secret Protection{% else %}Secret scanning{% endif %}'