The 2.16 series release notes contain important changes in this release series.
- Packages have been updated to the latest security versions.
- Backups of GitHub Enterprise Server clusters could intermittently fail due to duplicated Gist repository references.
- Transient, non-fatal errors returned from external LDAP servers during team synchronization operations could cause the incorrect removal of team members.
Upcoming deprecation of GitHub Enterprise Server 2.16
GitHub Enterprise Server 2.16 will be deprecated as of January 22, 2020 That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, upgrade to the newest version of GitHub Enterprise Server as soon as possible.
- 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.
- 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.
- The Let's Encrypt certificate registration feature consistently fails following an update to the external API.
The GitHub Team