Updating release notes for 3.16 and 3.17 with a known issue. (#56817)
Co-authored-by: Vanessa <vgrl@github.com>
This commit is contained in:
@@ -16,6 +16,8 @@ sections:
|
|||||||
- |
|
- |
|
||||||
Site administrators running migrations on GitHub Enterprise Server benefit from optimized performance for code scanning, as garbage collection-related `ts_analyses` migrations are combined into a single step. This reduces migration time and minimizes operational disruption during upgrades.
|
Site administrators running migrations on GitHub Enterprise Server benefit from optimized performance for code scanning, as garbage collection-related `ts_analyses` migrations are combined into a single step. This reduces migration time and minimizes operational disruption during upgrades.
|
||||||
known_issues:
|
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-23]
|
||||||
- |
|
- |
|
||||||
Custom firewall rules are removed during the upgrade process.
|
Custom firewall rules are removed during the upgrade process.
|
||||||
- |
|
- |
|
||||||
|
|||||||
@@ -16,6 +16,8 @@ sections:
|
|||||||
- |
|
- |
|
||||||
Site administrators running migrations on GitHub Enterprise Server benefit from optimized performance for code scanning, as garbage collection-related `ts_analyses` migrations are combined into a single step. This reduces migration time and minimizes operational disruption during upgrades.
|
Site administrators running migrations on GitHub Enterprise Server benefit from optimized performance for code scanning, as garbage collection-related `ts_analyses` migrations are combined into a single step. This reduces migration time and minimizes operational disruption during upgrades.
|
||||||
known_issues:
|
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-23]
|
||||||
- |
|
- |
|
||||||
Custom firewall rules are removed during the upgrade process.
|
Custom firewall rules are removed during the upgrade process.
|
||||||
- |
|
- |
|
||||||
|
|||||||
Reference in New Issue
Block a user