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

HIGH: The legacy avatar upgrade functionality was vulnerable to a Server-Side Request Forgery (SSRF) vulnerability when fetching image content from third-party avatar services. This could allow an attacker to make GET requests to internal services reachable from the GitHub Enterprise deployment.
LOW: The script-src: 'unsafe-inline' CSP header was applied to all paths for Enterprise Manager.
Packages have been updated to the latest security versions.

Promoting a replica in an active HA environment could fail to properly apply configuration changes and remove a pre-flight check holding page.
In certain cluster configurations, background jobs are unable to communicate with local storage services.
MySQL replication lag could rise significantly on high traffic instances during times of peak user activity.

GitHub Enterprise Server is now available in the eu-north-1 AWS region.
MySQL database seeding progress is reported during replication setup and recorded in the configuration log.

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.
When using Let's Encrypt with a new installation, an error can occur when creating a new Let's Encrypt account.

Thanks!

The GitHub Team