The 2.16 series release notes contain important changes in this release series.
- Certain high throughput conditions caused MySQL to consume a large amount of CPU time.
- Certain scenarios resulted in a sign out message being displayed incorrectly.
- Inefficient connection handling for an internal service created unnecessary log entries and in extreme cases could lead to a service outage.
- On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.
- Custom firewall rules aren't maintained during an upgrade.
- svn checkout may timeout while the repository data cache is being built. In most cases, subsequent svn checkout attempts will succeed.
- Git LFS tracked files uploaded through the web interface are incorrectly added directly to the repository.
- Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
- Some pull requests and issues are purged completely when restoring the repository right after deleting it.
- Resque workers may not be cleaned up following a configuration run leading to a growing number of stale workers which in turn could lead to high memory consumption. (updated 2019-05-08)
The GitHub Team