Merge pull request github#27403 from github/repo-sync

Repo sync
voxpelli · Aug 11, 2023 · 2768487 · 2768487
2 parents f4d80df + d6968e1
commit 2768487
Show file tree

Hide file tree

Showing 6 changed files with 12 additions and 6 deletions.
diff --git a/data/release-notes/enterprise-server/3-9/0.yml b/data/release-notes/enterprise-server/3-9/0.yml
@@ -381,7 +381,7 @@ sections:
 
   known_issues:
     - |
-      After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8 to 3.9, I/O utilization will increase, and in some cases the instance's performance will be impacted. Reduced performance is due to the database server being upgraded from MySQL 5.7 to MySQL 8.0. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance)."
+      {% data reusables.release-notes.upgrade-to-3-9-or-to-3-10-io-utilization-increase %}
     - |
       {% data reusables.release-notes.upgrade-mysql8-cannot-start-up %}
     - |

diff --git a/data/release-notes/enterprise-server/3-9/1.yml b/data/release-notes/enterprise-server/3-9/1.yml
@@ -100,7 +100,7 @@ sections:
       On an instance with multiple nodes, internal tooling to repair repositories now attempts to resolve problems within the entire repository network.
   known_issues:
     - |
-      After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8 to 3.9, I/O utilization will increase, and in some cases the instance's performance will be impacted. Reduced performance is due to the database server being upgraded from MySQL 5.7 to MySQL 8.0. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance)."
+      {% data reusables.release-notes.upgrade-to-3-9-or-to-3-10-io-utilization-increase %}
     - |
       {% data reusables.release-notes.upgrade-mysql8-cannot-start-up %}
     - |

diff --git a/data/release-notes/enterprise-server/3-9/3.yml b/data/release-notes/enterprise-server/3-9/3.yml
@@ -27,6 +27,10 @@ sections:
     - |
       Administrators can display all repositories in a network with `spokesctl` by using the `repositories` subcommand. 
   known_issues:
+    - |
+      {% data reusables.release-notes.upgrade-to-3-9-or-to-3-10-io-utilization-increase %} [Updated: 2023-08-11]
+    - |
+      {% data reusables.release-notes.upgrade-mysql8-cannot-start-up %}
     - |
       Custom firewall rules are removed during the upgrade process.
     - |
@@ -47,5 +51,4 @@ sections:
       On an instance with subdomain isolation disabled, Mermaid diagrams in the web UI display an "Unable to render rich display" error and fail to render.
     - |
       When enabling CodeQL via default setup [at scale](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-at-scale), some checks related to GitHub Actions are omitted, potentially preventing the process from completing.
-    - |
-      {% data reusables.release-notes.upgrade-mysql8-cannot-start-up %}
+
diff --git a/data/reusables/enterprise/upgrade-to-3-9-or-to-3-10-mysql-cannot-start-up.md b/data/reusables/enterprise/upgrade-to-3-9-or-to-3-10-mysql-cannot-start-up.md
@@ -1 +1 @@
-After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8, 3.9, or 3.10, MySQL may not start back up. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance#mysql-does-not-start-after-upgrade-to-github-enterprise-server-39)."
+After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8, to 3.9 or 3.10, MySQL may not start back up. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance#mysql-does-not-start-after-upgrade-to-github-enterprise-server-39)."
diff --git a/data/reusables/release-notes/upgrade-mysql8-cannot-start-up.md b/data/reusables/release-notes/upgrade-mysql8-cannot-start-up.md
@@ -1 +1 @@
-{% data reusables.enterprise.upgrade-to-3-9-or-to-3-10-mysql-cannot-start-up %} [Updated: 2023-07-27]
+{% data reusables.enterprise.upgrade-to-3-9-or-to-3-10-mysql-cannot-start-up %} [Updated: 2023-08-11]
diff --git a/data/reusables/release-notes/upgrade-to-3-9-or-to-3-10-io-utilization-increase.md b/data/reusables/release-notes/upgrade-to-3-9-or-to-3-10-io-utilization-increase.md
@@ -0,0 +1,3 @@
+After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8 to 3.9 or 3.10, I/O utilization will increase, and in some cases the instance's performance will be impacted. 
+Reduced performance is due to the database server being upgraded from MySQL 5.7 to MySQL 8.0. 
+For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance)."