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

Security Fixes

• Packages have been updated to the latest security versions.

Bug Fixes

• Pre-receive hooks would fail if the pre-receive environment lacked a /etc directory.
• Active git processes were not displayed on the Management Console's maintenance page
• Nameid-format matching on SAML response is too strict when value is "unspecified", which can cause an error with the "Another user already owns the account." message if the IdP changes NameID. (updated 2018-06-25)

Known Issues

• We incorrectly redirect to the dashboard if you accessed GitHub Enterprise using an alias while in private mode. This might happen if you set a fully qualified domain name but the subdomain resolves correctly.
• Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes.
• 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.
• GitHub Enterprise clustering can not be configured without https.
• Deleting a search index doesn't delete all associated metadata, which are then incorrectly reused if a new search index is created. This causes search index repair jobs to be reported as finished in the site admin when they were not.
• Pull request review comments migrated with ghe-migrator are displayed in the wrong order.
• The pull request review request has users reversed, after migration with ghe-migrator.
• The comment count in the "Conversation" tab of a pull request migrated with ghe-migrator can be wrong.
• The gpgverify service may consume large amounts of CPU time even when not processing requests.

Thanks!

The GitHub Team