Merge pull request #22397 from github/repo-sync

Octomerger · web-flow · commit f1384f92979c · 2022-11-30T23:34:08.000-08:00
repo sync
diff --git a/data/release-notes/enterprise-server/3-4/0.yml b/data/release-notes/enterprise-server/3-4/0.yml
@@ -258,6 +258,8 @@ sections:
       - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute.
       - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL.
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
   deprecations:
     - heading: Deprecation of GitHub Enterprise Server 3.0
       notes:
diff --git a/data/release-notes/enterprise-server/3-4/1.yml b/data/release-notes/enterprise-server/3-4/1.yml
@@ -55,6 +55,8 @@ sections:
       - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute.
       - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL.
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
   deprecations:
     - heading: Deprecation of GitHub Enterprise Server 3.0
       notes:
diff --git a/data/release-notes/enterprise-server/3-4/2.yml b/data/release-notes/enterprise-server/3-4/2.yml
@@ -31,6 +31,8 @@ sections:
       After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
   deprecations:
     - heading: Deprecation of GitHub Enterprise Server 3.0
       notes:
diff --git a/data/release-notes/enterprise-server/3-4/3.yml b/data/release-notes/enterprise-server/3-4/3.yml
@@ -37,4 +37,6 @@ sections:
     - |
       After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4 releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
-    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-4/4.yml b/data/release-notes/enterprise-server/3-4/4.yml
@@ -28,4 +28,6 @@ sections:
     - |
       After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
-    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-4/5.yml b/data/release-notes/enterprise-server/3-4/5.yml
@@ -27,4 +27,6 @@ sections:
     - |
       After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration.
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
-    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-4/6.yml b/data/release-notes/enterprise-server/3-4/6.yml
@@ -32,3 +32,5 @@ sections:
       After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-4/7.yml b/data/release-notes/enterprise-server/3-4/7.yml
@@ -24,3 +24,5 @@ sections:
       After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-4/8.yml b/data/release-notes/enterprise-server/3-4/8.yml
@@ -24,3 +24,5 @@ sections:
       After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-4/9.yml b/data/release-notes/enterprise-server/3-4/9.yml
@@ -39,4 +39,6 @@ sections:
       After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
-    - '{% data reusables.release-notes.2022-09-hotpatch-issue %}'
+    - '{% data reusables.release-notes.2022-09-hotpatch-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-5/0.yml b/data/release-notes/enterprise-server/3-5/0.yml
@@ -443,4 +443,6 @@ sections:
         - Reopening of dismissed Dependabot alerts
         - Enabling the **Update branch** button for all pull requests in a repository
         - Light high contrast theme
-      - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+      - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+      - |
+        GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-5/1.yml b/data/release-notes/enterprise-server/3-5/1.yml
@@ -41,3 +41,5 @@ sections:
         - Enabling the **Update branch** button for all pull requests in a repository
         - Light high contrast theme
       - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+      - |
+        GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-5/2.yml b/data/release-notes/enterprise-server/3-5/2.yml
@@ -41,4 +41,6 @@ sections:
         - Reopening of dismissed Dependabot alerts
         - Enabling the **Update branch** button for all pull requests in a repository
         - Light high contrast theme
-      - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+      - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+      - |
+        GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-5/3.yml b/data/release-notes/enterprise-server/3-5/3.yml
@@ -41,3 +41,5 @@ sections:
       - Enabling the **Update branch** button for all pull requests in a repository
       - Light high contrast theme
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-5/4.yml b/data/release-notes/enterprise-server/3-5/4.yml
@@ -27,4 +27,6 @@ sections:
     - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
-    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-5/5.yml b/data/release-notes/enterprise-server/3-5/5.yml
@@ -25,3 +25,5 @@ sections:
     - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-5/6.yml b/data/release-notes/enterprise-server/3-5/6.yml
@@ -38,4 +38,6 @@ sections:
     - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
-    - '{% data reusables.release-notes.2022-09-hotpatch-issue %}'
+    - '{% data reusables.release-notes.2022-09-hotpatch-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-5/7.yml b/data/release-notes/enterprise-server/3-5/7.yml
@@ -44,3 +44,5 @@ sections:
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
     - '{% data reusables.release-notes.2022-09-hotpatch-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-6/0.yml b/data/release-notes/enterprise-server/3-6/0.yml
@@ -300,3 +300,5 @@ sections:
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
     - |
       After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue, [contact {% data variables.contact.enterprise_support %}](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket). [Updated: 2022-10-03]
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-6/1.yml b/data/release-notes/enterprise-server/3-6/1.yml
@@ -33,3 +33,5 @@ sections:
     - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
     - |
       After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-6/2.yml b/data/release-notes/enterprise-server/3-6/2.yml
@@ -43,3 +43,5 @@ sections:
     - |
       After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
     - '{% data reusables.release-notes.2022-09-hotpatch-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
diff --git a/data/release-notes/enterprise-server/3-6/3.yml b/data/release-notes/enterprise-server/3-6/3.yml
@@ -51,3 +51,5 @@ sections:
     - In some cases, users cannot convert existing issues to discussions.
     - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
     - '{% data reusables.release-notes.2022-09-hotpatch-issue %}'
+    - |
+      GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
