GitHub Enterprise - The best way to build and ship software

The 2.16 series release notes contain important changes in this release series.

Security Fixes

Uploads of some image types could fail when using Git LFS 2.5.0 or newer.
Entries for the babeld.log, gitauth.log, production.log, resqued.log and unicorn.log log files were truncated when forwarded to a central log server.
Stricter REST API validation was prematurely enabled. As a result, API requests that previously succeeded may have been rejected with a 422 Unprocessable Entity response.
Viewing the global business profile page for organizations with a lot of users could timeout.
Restoring a backup containing a very large number of deleted repositories could fail with the error "Resource temporarily unavailable".
Repositories owned by organizations could not be deleted by organization owners if the Repository deletion and transfer business setting was set to Disabled.
Repository pages with a lot of tags and branches could take a very long time to load.

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. (updated 2019-03-07)
Some pull requests and issues are purged completely when restoring the repository right after deleting it. (updated 2019-03-19)
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)

Thanks!

The GitHub Team