Updating release notes for 3.16 and 3.17 with a known issue. (#56866)
Co-authored-by: Vanessa <vgrl@github.com>
This commit is contained in:
Pallavi
@@ -181,6 +181,8 @@ sections:
|
||||
Customers who have code scanning enabled may experience slower transitions when upgrading to version 3.16.0, due to changes in the data model that require data migration. We recommend testing this upgrade in a non-production environment first, as it could result in longer downtime than expected. [Updated: 2025-06-12]
|
||||
|
||||
known_issues:
|
||||
- |
|
||||
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 3.16 with caution. [Updated: 2025-07-28]
|
||||
- |
|
||||
{% data reusables.release-notes.2025-03-security-product-transition-bug %} [Updated: 2025-03-17]
|
||||
- |
|
||||
@@ -268,4 +270,4 @@ sections:
|
||||
- |
|
||||
The release notes previously mentioned Dependabot support for `pnpm` workspace catalogs, which did not ship in 3.16 and will ship in 3.17. [Updated: 2025-05-08]
|
||||
- |
|
||||
Customers who have code scanning enabled may experience slower transitions when upgrading to version 3.16.0, due to changes in the data model that require data migration. We recommend testing this upgrade in a non-production environment first, as it could result in longer downtime than expected. [Updated: 2025-06-12]
|
||||
Customers who have code scanning enabled may experience slower transitions when upgrading to version 3.16.0, due to changes in the data model that require data migration. We recommend testing this upgrade in a non-production environment first, as it could result in longer downtime than expected. [Updated: 2025-06-12]
|
||||
|
||||
@@ -28,6 +28,8 @@ sections:
|
||||
- |
|
||||
Update the bundled `actions/setup-dotnet` with the latest versions from https://github.com/actions/setup-dotnet.
|
||||
known_issues:
|
||||
- |
|
||||
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 3.16 with caution. [Updated: 2025-07-28]
|
||||
- |
|
||||
Upgrades to 3.16.1 may fail due to an error while migrating a secret scanning database. The `ghe-migrations` command output will include a `DelegatedBypassConfigurationNotNil` error. To recover, you can restore from a backup, fail over to a replica, or reach out to GitHub Support if you encounter this issue. [Updated: 2025-04-03]
|
||||
- |
|
||||
|
||||
@@ -32,6 +32,8 @@ sections:
|
||||
- |
|
||||
The `spokesctl info` and `spokesctl repos` commands now also show wikis that are part of a network.
|
||||
known_issues:
|
||||
- |
|
||||
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 3.16 with caution. [Updated: 2025-07-28]
|
||||
- |
|
||||
Custom firewall rules are removed during the upgrade process.
|
||||
- |
|
||||
|
||||
@@ -53,6 +53,8 @@ sections:
|
||||
- |
|
||||
Microsoft Exchange Online is retiring SMTP basic authentication in September 2025. If your GitHub Enterprise Server instance uses this method to send email, delivery may fail after the retirement date. Microsoft recommends switching to a supported alternative. As another option, you may consider using an SMTP OAuth proxy such as [email-oauth2-proxy](https://github.com/simonrob/email-oauth2-proxy), though this is not officially supported. For details and configuration guidance, see the [Microsoft announcement](https://techcommunity.microsoft.com/blog/exchange/exchange-online-to-retire-basic-auth-for-client-submission-smtp-auth/4114750) and the proxy’s [documentation](https://github.com/simonrob/email-oauth2-proxy/blob/main/emailproxy.config).
|
||||
known_issues:
|
||||
- |
|
||||
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 3.16 with caution. [Updated: 2025-07-28]
|
||||
- |
|
||||
Custom firewall rules are removed during the upgrade process.
|
||||
- |
|
||||
|
||||
@@ -43,6 +43,8 @@ sections:
|
||||
- |
|
||||
Site administrators who manage dependencies with the base-pinned image should no longer rely on the vulcanizer CLI, as it is in the process of being retired and replaced with vulcancli. Transition to vulcancli to ensure continued support and compatibility.
|
||||
known_issues:
|
||||
- |
|
||||
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 3.16 with caution. [Updated: 2025-07-28]
|
||||
- |
|
||||
Custom firewall rules are removed during the upgrade process.
|
||||
- |
|
||||
|
||||
@@ -18,6 +18,8 @@ sections:
|
||||
- |
|
||||
The babeld service no longer reports log messages about some common client-induced networking errors, reducing noise in the logs.
|
||||
known_issues:
|
||||
- |
|
||||
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 3.16 with caution. [Updated: 2025-07-28]
|
||||
- |
|
||||
Applying a new GitHub Enterprise Server license using the Management Console can sometimes fail with an HTTP 500 error.
|
||||
- |
|
||||
|
||||
@@ -178,6 +178,8 @@ sections:
|
||||
Users see a horizontal navigation bar at the top of their enterprise account. This update is designed to improve the user experience by providing a consistent, intuitive navigation structure that mirrors the rest of the GitHub experience.
|
||||
|
||||
known_issues:
|
||||
- |
|
||||
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 3.17 with caution. [Updated: 2025-07-28]
|
||||
- |
|
||||
Custom firewall rules are removed during the upgrade process.
|
||||
- |
|
||||
|
||||
@@ -43,6 +43,8 @@ sections:
|
||||
- |
|
||||
Site administrators who manage dependencies with the base-pinned image should no longer rely on the vulcanizer CLI, as it is in the process of being retired and replaced with vulcancli. Transition to vulcancli to ensure continued support and compatibility.
|
||||
known_issues:
|
||||
- |
|
||||
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 3.17 with caution. [Updated: 2025-07-28]
|
||||
- |
|
||||
Custom firewall rules are removed during the upgrade process.
|
||||
- |
|
||||
|
||||
@@ -24,6 +24,8 @@ sections:
|
||||
- |
|
||||
The babeld service no longer reports log messages about some common client-induced networking errors, reducing noise in the logs.
|
||||
known_issues:
|
||||
- |
|
||||
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 3.17 with caution. [Updated: 2025-07-28]
|
||||
- |
|
||||
Applying a new GitHub Enterprise Server license using the Management Console can sometimes fail with an HTTP 500 error.
|
||||
- |
|
||||
|
||||
Reference in New Issue
Block a user