Merge pull request #36761 from github/repo-sync

Repo sync

Author: docs-bot

data/release-notes/enterprise-server/3-12/15.yml

@@ -2,7 +2,7 @@ date: '2025-02-18'
 intro: |
   {% warning %}
 
-  **Warning**: For instances installed on Google Cloud Platform (GCP), hotpatches or upgrades to GitHub Enterprise Server version `3.12.15` will result errors being reported in the upgrade log. We recommend waiting for the next patch release to hotpatch or upgrade.
+  **Warning**: For instances installed on Google Cloud Platform (GCP), hotpatches to GitHub Enterprise Server version `3.12.15` will result in errors being reported in the upgrade log. We recommend hotpatching to a newer 3.12 version instead. [Updated: 2025-03-11]
 
   {% endwarning %}
 sections:
@@ -31,7 +31,7 @@ sections:
       The `ghe-live-migrations --init-target` command fails with a descriptive error message if the specified upgrade path is not supported.
   known_issues:
     - |
-      {% data reusables.release-notes.2025-02-gcp-hotpatch-bug %} [Updated: 2025-02-23]
+      {% data reusables.release-notes.2025-02-gcp-hotpatch-bug %} [Updated: 2025-03-11]
     - |
       Custom firewall rules are removed during the upgrade process.
     - |
@@ -56,3 +56,7 @@ sections:
       When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
     - |
       Some customers upgrading from 3.11.x or 3.12.x may experience a bug with the feature "Automatic update checks", filling the root disk with logs causing a system degradation. To prevent this, you can turn off the feature "[Enable automatic update check](/admin/upgrading-your-instance/preparing-to-upgrade/enabling-automatic-update-checks#enabling-automatic-update-checks)" in the management console.
+  
+  errata:
+    - |
+      The warning and known issues section have been updated to accurately reflect that instances installed on GCP will face issues while hotpatching to 3.12.15. Previously, the warning and known issue indicated that customers would face issues either while upgrading or hotpatching to version 3.12.15. [Updated: 2025-03-11]

data/release-notes/enterprise-server/3-13/11.yml

@@ -2,7 +2,7 @@ date: '2025-02-18'
 intro: |
   {% warning %}
 
-  **Warning**: For instances installed on Google Cloud Platform (GCP), hotpatches or upgrades to GitHub Enterprise Server version `3.13.11` will result errors being reported in the upgrade log. We recommend waiting for the next patch release to hotpatch or upgrade.
+  **Warning**: For instances installed on Google Cloud Platform (GCP), hotpatches to GitHub Enterprise Server version `3.13.11` will result in errors being reported in the upgrade log. We recommend hotpatching to a newer 3.13 version instead. [Updated: 2025-03-11]
 
   {% endwarning %}
 sections:
@@ -41,7 +41,7 @@ sections:
       The `ghe-live-migrations --init-target` command fails with a descriptive error message if the specified upgrade path is not supported.
   known_issues:
     - |
-      {% data reusables.release-notes.2025-02-gcp-hotpatch-bug %} [Updated: 2025-02-23]
+      {% data reusables.release-notes.2025-02-gcp-hotpatch-bug %} [Updated: 2025-03-11]
     - |
       During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
     - |
@@ -62,3 +62,7 @@ sections:
       When restoring data originally backed up from a 3.13 appliance onto a 3.13 appliance, the elasticsearch indices need to be reindexed before some of the data will show up.  This happens via a nightly scheduled job.  It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`.
     - |
       When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
+      
+  errata:
+    - |
+      The warning and known issues section have been updated to accurately reflect that instances installed on GCP will face issues while hotpatching to 3.13.11. Previously, the warning and known issue indicated that customers would face issues either while upgrading or hotpatching to version 3.13.11. [Updated: 2025-03-11]

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

@@ -2,7 +2,7 @@ date: '2025-02-18'
 intro: |
   {% warning %}
 
-  **Warning**: For instances installed on Google Cloud Platform (GCP), hotpatches or upgrades to GitHub Enterprise Server version `3.14.8` will result errors being reported in the upgrade log. We recommend waiting for the next patch release to hotpatch or upgrade.
+  **Warning**: For instances installed on Google Cloud Platform (GCP), hotpatches to GitHub Enterprise Server version `3.14.8` will result in errors being reported in the upgrade log. We recommend hotpatching to a newer 3.14 version instead. [Updated: 2025-03-11]
 
   {% endwarning %}
 sections:
@@ -49,7 +49,7 @@ sections:
       The `ghe-live-migrations --init-target` command fails with a descriptive error message if the  specified upgrade path is not supported.
   known_issues:
     - |
-      {% data reusables.release-notes.2025-02-gcp-hotpatch-bug %} [Updated: 2025-02-23]
+      {% data reusables.release-notes.2025-02-gcp-hotpatch-bug %} [Updated: 2025-03-11]
     - |
       During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
     - |
@@ -80,3 +80,7 @@ sections:
       When enabling automatic update checks for the first time in the Management Console, the status is not dynamically reflected until the "Updates" page is reloaded.
     - |
       When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
+  
+  errata:
+    - |
+      The warning and known issues section have been updated to accurately reflect that instances installed on GCP will face issues while hotpatching to 3.14.8. Previously, the warning and known issue indicated that customers would face issues either while upgrading or hotpatching to version 3.14.8. [Updated: 2025-03-11]

data/release-notes/enterprise-server/3-15/3.yml

@@ -2,7 +2,7 @@ date: '2025-02-18'
 intro: |
   {% warning %}
 
-  **Warning**: For instances installed on Google Cloud Platform (GCP), hotpatches or upgrades to GitHub Enterprise Server version `3.15.3` will result errors being reported in the upgrade log. We recommend waiting for the next patch release to hotpatch or upgrade.
+  **Warning**: For instances installed on Google Cloud Platform (GCP), hotpatches to GitHub Enterprise Server version `3.15.3` will result in errors being reported in the upgrade log. We recommend hotpatching to a newer 3.15 version instead. [Updated: 2025-03-11]
 
   {% endwarning %}
 sections:
@@ -53,7 +53,7 @@ sections:
       The `ghe-live-migrations --init-target` command fails with a descriptive error message if the specified upgrade path is not supported.
   known_issues:
     - |
-      {% data reusables.release-notes.2025-02-gcp-hotpatch-bug %} [Updated: 2025-02-23]
+      {% data reusables.release-notes.2025-02-gcp-hotpatch-bug %} [Updated: 2025-03-11]
     - |
       During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
     - |
@@ -88,3 +88,7 @@ sections:
       When initializing a new GHES cluster, nodes with the `consul-server` role should be added to the cluster before adding additional nodes. Adding all nodes simultaneously creates a race condition between nomad server registration and nomad client registration.
     - |
       Admins setting up cluster high availability (HA) may encounter a spokes error when running `ghe-cluster-repl-status` if a new organization and repositories are created before using the `ghe-cluster-repl-bootstrap` command. To avoid this issue, complete the cluster HA setup with `ghe-cluster-repl-bootstrap` before creating new organizations and repositories.
+  
+  errata:
+    - |
+      The warning and known issues section have been updated to accurately reflect that instances installed on GCP will face issues while hotpatching to 3.15.3. Previously, the warning and known issue indicated that customers would face issues either while upgrading or hotpatching to version 3.15.3. [Updated: 2025-03-11]

data/release-notes/enterprise-server/3-16/0-rc1.yml

@@ -1,6 +1,6 @@
 date: '2025-02-25'
 release_candidate: true
-deprecated: false
+deprecated: true
 intro: |
   > [!NOTE] Release candidate (RC) builds are intended solely for use in a test environment. Do not install an RC in a production environment.
   >