diff --git a/data/release-notes/enterprise-server/3-15/0.yml b/data/release-notes/enterprise-server/3-15/0.yml index 92cbb3f5ad..0fbd10fa45 100644 --- a/data/release-notes/enterprise-server/3-15/0.yml +++ b/data/release-notes/enterprise-server/3-15/0.yml @@ -204,8 +204,10 @@ sections: On Azure instances, a failed pre-upgrade check due to insufficient user disk size can result in the Management Console displaying an `Internal Server Error`. To restore access to the Management Console, run `sudo rm /var/log/preflight-check-report.json` to remove the file. If enabled, the `automatic update checks` need to be disabled from the Management Console until user disk size is increased to minimum 500 GB. To increase the user disk size, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity#increasing-the-data-partition-size). - | {% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %} + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. - [Updated: 2025-03-12] + [Updated: 2025-11-24] closing_down: # https://github.com/github/releases/issues/3525 diff --git a/data/release-notes/enterprise-server/3-15/1.yml b/data/release-notes/enterprise-server/3-15/1.yml index 40e99e1546..604c80ca22 100644 --- a/data/release-notes/enterprise-server/3-15/1.yml +++ b/data/release-notes/enterprise-server/3-15/1.yml @@ -94,8 +94,10 @@ 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. - | {% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %} + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. - [Updated: 2025-03-12] + [Updated: 2025-11-24] deprecations: # https://github.com/github/releases/issues/4037 diff --git a/data/release-notes/enterprise-server/3-15/10.yml b/data/release-notes/enterprise-server/3-15/10.yml index 56b8aa0526..83ca16227d 100644 --- a/data/release-notes/enterprise-server/3-15/10.yml +++ b/data/release-notes/enterprise-server/3-15/10.yml @@ -54,3 +54,7 @@ sections: 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. - | After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-15/11.yml b/data/release-notes/enterprise-server/3-15/11.yml index b60e4b90a3..38a62143df 100644 --- a/data/release-notes/enterprise-server/3-15/11.yml +++ b/data/release-notes/enterprise-server/3-15/11.yml @@ -64,3 +64,7 @@ sections: The autolink references feature is missing from the repository settings page. - | When attempting to open a pull request as a draft in a private or internal repository, users are incorrectly prompted to upgrade their plan.[Updated: 2025-08-11] + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-15/12.yml b/data/release-notes/enterprise-server/3-15/12.yml index 9437c6a310..07607aeb84 100644 --- a/data/release-notes/enterprise-server/3-15/12.yml +++ b/data/release-notes/enterprise-server/3-15/12.yml @@ -68,3 +68,7 @@ sections: 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. - | After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-15/13.yml b/data/release-notes/enterprise-server/3-15/13.yml index b70437db3a..c809f31d1b 100644 --- a/data/release-notes/enterprise-server/3-15/13.yml +++ b/data/release-notes/enterprise-server/3-15/13.yml @@ -60,3 +60,7 @@ sections: After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. - | Unexpected elements may appear in the UI on the repo overview page for locked repositories. + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. + + [Updated: 2025-11-24] \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-15/2.yml b/data/release-notes/enterprise-server/3-15/2.yml index c4afb1c06a..b143c89c9d 100644 --- a/data/release-notes/enterprise-server/3-15/2.yml +++ b/data/release-notes/enterprise-server/3-15/2.yml @@ -81,8 +81,10 @@ sections: 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. - | {% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %} + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. - [Updated: 2025-03-12] + [Updated: 2025-11-24] errata: - | diff --git a/data/release-notes/enterprise-server/3-15/3.yml b/data/release-notes/enterprise-server/3-15/3.yml index e93def00ad..abbdcb30ec 100644 --- a/data/release-notes/enterprise-server/3-15/3.yml +++ b/data/release-notes/enterprise-server/3-15/3.yml @@ -93,8 +93,10 @@ sections: 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. - | {% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %} + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. - [Updated: 2025-03-12] + [Updated: 2025-11-24] 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] diff --git a/data/release-notes/enterprise-server/3-15/4.yml b/data/release-notes/enterprise-server/3-15/4.yml index 84a9e3df7a..9f040cc37b 100644 --- a/data/release-notes/enterprise-server/3-15/4.yml +++ b/data/release-notes/enterprise-server/3-15/4.yml @@ -75,6 +75,10 @@ sections: [Updated: 2025-03-19] - | After a restore, existing outside collaborators are unable to be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. + + [Updated: 2025-11-24] errata: - | The release notes previously did not mention VMware ESXi 8.0 support. [Updated: 2025-04-02] diff --git a/data/release-notes/enterprise-server/3-15/5.yml b/data/release-notes/enterprise-server/3-15/5.yml index b7740b2a2a..9b68a1b124 100644 --- a/data/release-notes/enterprise-server/3-15/5.yml +++ b/data/release-notes/enterprise-server/3-15/5.yml @@ -60,3 +60,7 @@ sections: 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. - | After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-15/6.yml b/data/release-notes/enterprise-server/3-15/6.yml index 120f7d4fc9..94cd49fe59 100644 --- a/data/release-notes/enterprise-server/3-15/6.yml +++ b/data/release-notes/enterprise-server/3-15/6.yml @@ -62,3 +62,7 @@ sections: After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. - | Repository Cache Replicas return `Repository not found` when changes have been pushed to the Primary instance that have not yet synchronized to the Cache Replica. This issue can also occur in all previous patches of this release. + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-15/7.yml b/data/release-notes/enterprise-server/3-15/7.yml index 99f2ad9281..a328c49ebf 100644 --- a/data/release-notes/enterprise-server/3-15/7.yml +++ b/data/release-notes/enterprise-server/3-15/7.yml @@ -97,6 +97,10 @@ sections: Administrators 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. - | After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. + + [Updated: 2025-11-24] errata: - | diff --git a/data/release-notes/enterprise-server/3-15/8.yml b/data/release-notes/enterprise-server/3-15/8.yml index 57f1ed7ceb..7fc130f0ed 100644 --- a/data/release-notes/enterprise-server/3-15/8.yml +++ b/data/release-notes/enterprise-server/3-15/8.yml @@ -71,3 +71,7 @@ sections: 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. - | After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-15/9.yml b/data/release-notes/enterprise-server/3-15/9.yml index d3f3bc833c..7216ca6103 100644 --- a/data/release-notes/enterprise-server/3-15/9.yml +++ b/data/release-notes/enterprise-server/3-15/9.yml @@ -56,3 +56,7 @@ sections: 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. - | After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. + - | + Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-16/0.yml b/data/release-notes/enterprise-server/3-16/0.yml index ebcf5ce8e5..13780b9b4d 100644 --- a/data/release-notes/enterprise-server/3-16/0.yml +++ b/data/release-notes/enterprise-server/3-16/0.yml @@ -228,6 +228,10 @@ sections: [Updated: 2025-03-19] - | The security risk page returns a 500 error when secret scanning is disabled. [Updated: 2025-04-25] + - | + Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher. + + [Updated: 2025-11-24] closing_down: # https://github.com/github/releases/issues/4683 diff --git a/data/release-notes/enterprise-server/3-16/1.yml b/data/release-notes/enterprise-server/3-16/1.yml index 5f2cd10015..4499519e18 100644 --- a/data/release-notes/enterprise-server/3-16/1.yml +++ b/data/release-notes/enterprise-server/3-16/1.yml @@ -80,6 +80,10 @@ sections: After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows. - | The security risk page returns a 500 error when secret scanning is disabled. [Updated: 2025-04-25] + - | + Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher. + + [Updated: 2025-11-24] errata: - | Known issues incorrectly indicated that administrators could immediately run the `/usr/local/share/enterprise/ghe-es-search-repair` script after a restore to resolve indexing and collaborator access issues. In reality, this script must be run only after the system has been up for at least one hour. [Updated: 2025-04-22] diff --git a/data/release-notes/enterprise-server/3-16/2.yml b/data/release-notes/enterprise-server/3-16/2.yml index 7a6bd5cbb6..e363cd8774 100644 --- a/data/release-notes/enterprise-server/3-16/2.yml +++ b/data/release-notes/enterprise-server/3-16/2.yml @@ -84,3 +84,7 @@ sections: Repository Cache Replicas return `Repository not found` when changes have been pushed to the Primary instance that have not yet synchronized to the Cache Replica. This issue can also occur in all previous patches of this release. - | The security risk page returns a 500 error when secret scanning is disabled. [Updated: 2025-04-25] + - | + Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-16/3.yml b/data/release-notes/enterprise-server/3-16/3.yml index 7809bb0edb..996861fa31 100644 --- a/data/release-notes/enterprise-server/3-16/3.yml +++ b/data/release-notes/enterprise-server/3-16/3.yml @@ -99,6 +99,10 @@ sections: After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. - | After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows. + - | + Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher. + + [Updated: 2025-11-24] errata: - | diff --git a/data/release-notes/enterprise-server/3-16/4.yml b/data/release-notes/enterprise-server/3-16/4.yml index f465299d53..8489c607a0 100644 --- a/data/release-notes/enterprise-server/3-16/4.yml +++ b/data/release-notes/enterprise-server/3-16/4.yml @@ -89,3 +89,7 @@ sections: After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. - | After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows. + - | + Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-16/5.yml b/data/release-notes/enterprise-server/3-16/5.yml index cb5d5a3e2a..b92b350a93 100644 --- a/data/release-notes/enterprise-server/3-16/5.yml +++ b/data/release-notes/enterprise-server/3-16/5.yml @@ -66,3 +66,7 @@ sections: After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. - | After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows. + - | + Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-16/6.yml b/data/release-notes/enterprise-server/3-16/6.yml index 9c3323186e..5d68ebf4da 100644 --- a/data/release-notes/enterprise-server/3-16/6.yml +++ b/data/release-notes/enterprise-server/3-16/6.yml @@ -64,3 +64,7 @@ sections: After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows. - | In some scenarios, upgrades from GHES 3.14.x to 3.16 can fail with a migration error. Running `ghe-single-config-apply` _should_ allow the migration to proceed, and complete the upgrade. This will be fixed in GHES 3.16.7. To work around this issue, in your Enterprise's Code Security Settings, disable all security settings that apply to "new repositories". Once upgraded, create an Enterprise Security Configuration with your desired settings and set that configuration as the default for new repositories. + - | + Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-16/7.yml b/data/release-notes/enterprise-server/3-16/7.yml index 9b274f069b..9792c70591 100644 --- a/data/release-notes/enterprise-server/3-16/7.yml +++ b/data/release-notes/enterprise-server/3-16/7.yml @@ -78,3 +78,7 @@ sections: The autolink references feature is missing from the repository settings page. - | When attempting to open a pull request as a draft in a private or internal repository, users are incorrectly prompted to upgrade their plan.[Updated: 2025-08-11] + - | + Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-16/8.yml b/data/release-notes/enterprise-server/3-16/8.yml index 68149a8860..fdf89e1fed 100644 --- a/data/release-notes/enterprise-server/3-16/8.yml +++ b/data/release-notes/enterprise-server/3-16/8.yml @@ -80,3 +80,7 @@ sections: After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows. - | Customers operating at high scale or near capacity may experience unexpected performance degradation, such as slow response times, background job queue spikes, elevated CPU usage, and increased MySQL load. Consider upgrading to {% ifversion ghes = 3.16 %}3.16{% endif %}{% ifversion ghes = 3.17 %}3.17{% endif %}{% ifversion ghes = 3.18 %}3.18{% endif %} with caution. + - | + Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-16/9.yml b/data/release-notes/enterprise-server/3-16/9.yml index e6113025f7..a842f5d1cc 100644 --- a/data/release-notes/enterprise-server/3-16/9.yml +++ b/data/release-notes/enterprise-server/3-16/9.yml @@ -70,4 +70,8 @@ sections: After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows. - | Unexpected elements may appear in the UI on the repo overview page for locked repositories. + - | + Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher. + + [Updated: 2025-11-24] \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-17/0.yml b/data/release-notes/enterprise-server/3-17/0.yml index 0ba97fee3b..bd145acc55 100644 --- a/data/release-notes/enterprise-server/3-17/0.yml +++ b/data/release-notes/enterprise-server/3-17/0.yml @@ -218,6 +218,10 @@ sections: When publishing npm packages in a workflow after restoring from a backup to GitHub Enterprise Server 3.13.5.gm4 or 3.14.2.gm3, you may encounter a `401 Unauthorized` error from the GitHub Packages service. This can happen if the restore is from an N-1 or N-2 version and the workflow targets the npm endpoint on the backup instance. To avoid this issue, ensure the access token is valid and includes the correct scopes for publishing to GitHub Packages. - | Uploading a new license with unbundled GitHub Advanced Security may not fully unbundle all the Security Configurations on the instance in certain cases. Any active Security Configurations will continue to function, but when attempting to apply the configurations to new repositories you may see errors like "Advanced Security is not purchased" or `Validation failed: Secret scanning non provider patterns Non-provider patterns must be disabled when secret scanning is disabled`. Contact GitHub Support for assistance clearing this state in version 3.17.0. This issue will be resolved in version 3.17.2. + - | + Upgrading to this version from GHES 3.15.14 and higher or 3.16.10 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.17.7 or higher. + + [Updated: 2025-11-24] closing_down: # https://github.com/github/releases/issues/5177 diff --git a/data/release-notes/enterprise-server/3-17/1.yml b/data/release-notes/enterprise-server/3-17/1.yml index f8d674c817..ac13e10d03 100644 --- a/data/release-notes/enterprise-server/3-17/1.yml +++ b/data/release-notes/enterprise-server/3-17/1.yml @@ -83,3 +83,7 @@ sections: When publishing npm packages in a workflow after restoring from a backup to GitHub Enterprise Server 3.13.5.gm4 or 3.14.2.gm3, you may encounter a `401 Unauthorized` error from the GitHub Packages service. This can happen if the restore is from an N-1 or N-2 version and the workflow targets the npm endpoint on the backup instance. To avoid this issue, ensure the access token is valid and includes the correct scopes for publishing to GitHub Packages. - | Uploading a new license with unbundled GitHub Advanced Security may not fully unbundle all the Security Configurations on the instance in certain cases. Any active Security Configurations will continue to function, but when attempting to apply the configurations to new repositories you may see errors like "Advanced Security is not purchased" or `Validation failed: Secret scanning non provider patterns. Non-provider patterns must be disabled when secret scanning is disabled`. Contact GitHub Support for assistance clearing this state in version 3.17.1. This issue will be resolved in version 3.17.2. + - | + Upgrading to this version from GHES 3.15.14 and higher or 3.16.10 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.17.7 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-17/2.yml b/data/release-notes/enterprise-server/3-17/2.yml index c2b4f79275..d3d39d2dcc 100644 --- a/data/release-notes/enterprise-server/3-17/2.yml +++ b/data/release-notes/enterprise-server/3-17/2.yml @@ -64,3 +64,7 @@ sections: After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows. - | When publishing npm packages in a workflow after restoring from a backup to GitHub Enterprise Server 3.13.5.gm4 or 3.14.2.gm3, you may encounter a `401 Unauthorized` error from the GitHub Packages service. This can happen if the restore is from an N-1 or N-2 version and the workflow targets the npm endpoint on the backup instance. To avoid this issue, ensure the access token is valid and includes the correct scopes for publishing to GitHub Packages. + - | + Upgrading to this version from GHES 3.15.14 and higher or 3.16.10 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.17.7 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-17/3.yml b/data/release-notes/enterprise-server/3-17/3.yml index 3980717374..76e575a43b 100644 --- a/data/release-notes/enterprise-server/3-17/3.yml +++ b/data/release-notes/enterprise-server/3-17/3.yml @@ -54,3 +54,7 @@ sections: After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows. - | When publishing npm packages in a workflow after restoring from a backup to GitHub Enterprise Server 3.13.5.gm4 or 3.14.2.gm3, you may encounter a `401 Unauthorized` error from the GitHub Packages service. This can happen if the restore is from an N-1 or N-2 version and the workflow targets the npm endpoint on the backup instance. To avoid this issue, ensure the access token is valid and includes the correct scopes for publishing to GitHub Packages. + - | + Upgrading to this version from GHES 3.15.14 and higher or 3.16.10 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.17.7 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-17/4.yml b/data/release-notes/enterprise-server/3-17/4.yml index 263e0aff72..d7d1625304 100644 --- a/data/release-notes/enterprise-server/3-17/4.yml +++ b/data/release-notes/enterprise-server/3-17/4.yml @@ -74,3 +74,7 @@ sections: The autolink references feature is missing from the repository settings page. - | When attempting to open a pull request as a draft in a private or internal repository, users are incorrectly prompted to upgrade their plan.[Updated: 2025-08-11] + - | + Upgrading to this version from GHES 3.15.14 and higher or 3.16.10 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.17.7 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-17/5.yml b/data/release-notes/enterprise-server/3-17/5.yml index c37f1458f9..db64211f72 100644 --- a/data/release-notes/enterprise-server/3-17/5.yml +++ b/data/release-notes/enterprise-server/3-17/5.yml @@ -82,3 +82,7 @@ sections: When publishing npm packages in a workflow after restoring from a backup to GitHub Enterprise Server 3.13.5.gm4 or 3.14.2.gm3, you may encounter a `401 Unauthorized` error from the GitHub Packages service. This can happen if the restore is from an N-1 or N-2 version and the workflow targets the npm endpoint on the backup instance. To avoid this issue, ensure the access token is valid and includes the correct scopes for publishing to GitHub Packages. - | Customers operating at high scale or near capacity may experience unexpected performance degradation, such as slow response times, background job queue spikes, elevated CPU usage, and increased MySQL load. Consider upgrading to {% ifversion ghes = 3.16 %}3.16{% endif %}{% ifversion ghes = 3.17 %}3.17{% endif %}{% ifversion ghes = 3.18 %}3.18{% endif %} with caution. + - | + Upgrading to this version from GHES 3.15.14 and higher or 3.16.10 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.17.7 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-17/6.yml b/data/release-notes/enterprise-server/3-17/6.yml index a1267b677c..929858f979 100644 --- a/data/release-notes/enterprise-server/3-17/6.yml +++ b/data/release-notes/enterprise-server/3-17/6.yml @@ -76,3 +76,7 @@ sections: Unexpected elements may appear in the UI on the repo overview page for locked repositories. - | When publishing npm packages in a workflow after restoring from a backup to GitHub Enterprise Server 3.13.5.gm4 or 3.14.2.gm3, you may encounter a `401 Unauthorized` error from the GitHub Packages service. This can happen if the restore is from an N-1 or N-2 version and the workflow targets the npm endpoint on the backup instance. To avoid this issue, ensure the access token is valid and includes the correct scopes for publishing to GitHub Packages. + - | + Upgrading to this version from GHES 3.15.14 and higher or 3.16.10 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.17.7 or higher. + + [Updated: 2025-11-24] diff --git a/data/release-notes/enterprise-server/3-18/0.yml b/data/release-notes/enterprise-server/3-18/0.yml index 704fb14e91..3aac7a5556 100644 --- a/data/release-notes/enterprise-server/3-18/0.yml +++ b/data/release-notes/enterprise-server/3-18/0.yml @@ -222,6 +222,10 @@ sections: When publishing npm packages in a workflow after restoring from a backup to GitHub Enterprise Server 3.13.5.gm4 or 3.14.2.gm3, you may encounter a `401 Unauthorized` error from the GitHub Packages service. This can happen if the restore is from an N-1 or N-2 version and the workflow targets the npm endpoint on the backup instance. To avoid this issue, ensure the access token is valid and includes the correct scopes for publishing to GitHub Packages. - | The entry for Private Registries in the organization settings menu is not visible unless Dependabot is enabled. + - | + Upgrading to this version from GHES 3.16.10 and higher or 3.17.6 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.18.1 or higher. + + [Updated: 2025-11-24] closing_down: # https://github.com/github/releases/issues/5177