Repo sync

data/release-notes/enterprise-server/3-20/6.yml

@@ -97,4 +97,4 @@ sections:
     - |
       On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`.
     - |
-      When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored.  [Updated: 2026-08-27]
+      When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Replication Controller is disabled by default in {% data variables.product.prodname_ghe_server %} 3.20. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22]

data/release-notes/enterprise-server/3-20/7.yml

@@ -90,4 +90,4 @@ sections:
     - |
       On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`.
     - |
-      When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored.
+      When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Replication Controller is disabled by default in {% data variables.product.prodname_ghe_server %} 3.20. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22]

data/release-notes/enterprise-server/3-20/8.yml

@@ -110,4 +110,4 @@ sections:
     - |
       On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`.
     - |
-      _When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored._
+      When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Replication Controller is disabled by default in {% data variables.product.prodname_ghe_server %} 3.20. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22]

data/release-notes/enterprise-server/3-20/9.yml

@@ -66,7 +66,7 @@ sections:
     - |
       On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`.
     - |
-      When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored.
+      When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Replication Controller is disabled by default in {% data variables.product.prodname_ghe_server %} 3.20. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22]
   errata:
     - |
       The known issues incorrectly indicated that Elasticsearch indices are reindexed by a nightly scheduled job after restoring data backed up from GitHub Enterprise Server 3.13 or later. The scheduled job runs on the first Saturday of each month. [Updated: 2026-10-15]

data/release-notes/enterprise-server/3-21/4.yml

@@ -96,4 +96,4 @@ sections:
     - |
       On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`.
     - |
-      When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored. [Updated: 2026-08-27]
+      When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, which is the default in {% data variables.product.prodname_ghe_server %} 3.21, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Restores with {% data variables.product.prodname_enterprise_backup_service %} on {% data variables.product.prodname_ghe_server %} 3.21.6 or later aren't affected. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22]

data/release-notes/enterprise-server/3-21/5.yml

@@ -96,6 +96,6 @@ sections:
     - |
       After upgrading to GHES 3.21, scheduled Dependabot version updates may stop running for pre-existing configurations. If you have already upgraded and want to trigger scheduled version updates, save a change to each affected repository’s `.github/dependabot.yml` file.
     - |
-      When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored.
+      When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, which is the default in {% data variables.product.prodname_ghe_server %} 3.21, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Restores with {% data variables.product.prodname_enterprise_backup_service %} on {% data variables.product.prodname_ghe_server %} 3.21.6 or later aren't affected. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22]
     - |
       In clustered GitHub Enterprise Server environments, administrators may find that nodes that remain in the cluster but no longer have the `git-server`, `pages-server`, or `storage-server` role remain online and eligible to vote in the corresponding replication tables. Review role-specific replication state and contact GitHub Support if stale rows affect replication.

data/release-notes/enterprise-server/3-21/6.yml

@@ -124,6 +124,6 @@ sections:
     - |
       In clustered GitHub Enterprise Server environments, administrators may find that nodes that remain in the cluster but no longer have the `git-server`, `pages-server`, or `storage-server` role remain online and eligible to vote in the corresponding replication tables. Review role-specific replication state and contact GitHub Support if stale rows affect replication.
     - |
-      _When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored._
+      When an administrator uses {% data variables.product.prodname_enterprise_backup_utilities %} to restore a backup to a configured standalone instance with Replication Controller enabled, which is the default in {% data variables.product.prodname_ghe_server %} 3.21, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Restores with {% data variables.product.prodname_enterprise_backup_service %} on {% data variables.product.prodname_ghe_server %} 3.21.6 or later aren't affected. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22]
     - |
       _On a newly booted {% data variables.product.prodname_ghe_server %} instance, the merge box on a newly created pull request can stay on "Checking for the ability to merge automatically" and not show the merge status. If encountered, refreshing the page shows the correct merge status._

data/release-notes/enterprise-server/3-21/7.yml

@@ -72,7 +72,7 @@ sections:
     - |
       In a clustered GitHub Enterprise Server environment, a node that remained in the cluster after losing the `git-server`, `pages-server`, or `storage-server` role could continue to appear online and eligible for replication. This could cause replica placement failures, incorrect replica counts, or replication status to show a node without the relevant service as healthy. If you experience these symptoms, contact GitHub Support.
     - |
-      When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored.
+      When an administrator uses {% data variables.product.prodname_enterprise_backup_utilities %} to restore a backup to a configured standalone instance with Replication Controller enabled, which is the default in {% data variables.product.prodname_ghe_server %} 3.21, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Restores with {% data variables.product.prodname_enterprise_backup_service %} on {% data variables.product.prodname_ghe_server %} 3.21.6 or later aren't affected. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22]
     - |
       On a newly booted {% data variables.product.prodname_ghe_server %} instance, the merge box on a newly created pull request can stay on "Checking for the ability to merge automatically" and not show the merge status. If encountered, refreshing the page shows the correct merge status.
   errata:

data/release-notes/enterprise-server/3-22/0.yml

@@ -238,7 +238,7 @@ sections:
     - |
       After upgrading to {% data variables.product.prodname_ghe_server %} 3.22, scheduled {% data variables.product.prodname_dependabot_version_updates %} may stop running for pre-existing configurations. If you have already upgraded and want to trigger scheduled version updates, save a change to each affected repository's `.github/dependabot.yml` file.
     - |
-      When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored.
+      When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. This issue is fixed in {% data variables.product.prodname_ghe_server %} 3.22.1. If you see this warning or storage data is missing after a restore on {% data variables.product.prodname_ghe_server %} 3.22.0, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22]
     - |
       In clustered {% data variables.product.prodname_ghe_server %} environments, nodes that remain in the cluster after losing the `git-server`, `pages-server`, or `storage-server` role may stay online and remain eligible to vote in the corresponding replication tables. Review the replication state for each role, and contact {% data variables.contact.github_support %} if stale rows affect replication.
     - |      

data/release-notes/enterprise-server/3-22/1.yml

@@ -119,7 +119,8 @@ sections:
       After upgrading to GHES 3.21, scheduled Dependabot version updates may stop running for pre-existing configurations. If you have already upgraded and want to trigger scheduled version updates, save a change to each affected repository’s `.github/dependabot.yml` file.
     - |
       In clustered GitHub Enterprise Server environments, administrators may find that nodes that remain in the cluster but no longer have the `git-server`, `pages-server`, or `storage-server` role remain online and eligible to vote in the corresponding replication tables. Review role-specific replication state and contact GitHub Support if stale rows affect replication.
-    - |
-      _When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored._
     - |
       _On a newly booted {% data variables.product.prodname_ghe_server %} instance, the merge box on a newly created pull request can stay on "Checking for the ability to merge automatically" and not show the merge status. If encountered, refreshing the page shows the correct merge status._
+  errata:
+    - |
+      The known issues incorrectly indicated that this release doesn't restore the storage directory when you restore an instance with `ghe-restore` while Replication Controller is enabled. This issue is fixed in this release. [Updated: 2026-10-22]

data/release-notes/enterprise-server/3-22/2.yml

@@ -68,10 +68,10 @@ sections:
       After upgrading to GHES 3.21, scheduled Dependabot version updates may stop running for pre-existing configurations. If you have already upgraded and want to trigger scheduled version updates, save a change to each affected repository’s `.github/dependabot.yml` file.
     - |
       In a clustered GitHub Enterprise Server environment, a node that remained in the cluster after losing the `git-server`, `pages-server`, or `storage-server` role could continue to appear online and eligible for replication. This could cause replica placement failures, incorrect replica counts, or replication status to show a node without the relevant service as healthy. If you experience these symptoms, contact GitHub Support.
-    - |
-      When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored.
     - |
       On a newly booted {% data variables.product.prodname_ghe_server %} instance, the merge box on a newly created pull request can stay on "Checking for the ability to merge automatically" and not show the merge status. If encountered, refreshing the page shows the correct merge status.
   errata:
     - |
       The known issues incorrectly indicated that Elasticsearch indices are reindexed by a nightly scheduled job after restoring data backed up from GitHub Enterprise Server 3.13 or later. The scheduled job runs on the first Saturday of each month. [Updated: 2026-10-15]
+    - |
+      The known issues incorrectly indicated that this release doesn't restore the storage directory when you restore an instance with `ghe-restore` while Replication Controller is enabled. This issue was fixed in {% data variables.product.prodname_ghe_server %} 3.22.1. [Updated: 2026-10-22]