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

Security Fixes

• HIGH: Improper sanitization of user markup content, while not allowing full XSS, could have been abused to leak sensitive data or perform actions as the user viewing the content.
• LOW: Detect and reject any Git content that shows evidence of being part of a SHA-1 collision attack.
• Packages have been updated to the latest security versions.

Bug Fixes

• The webhook delivery log was missing timing metrics.
• The /trending page could incorrectly display a Sign up for free button.
• The total number of organizations was incorrect because the count included trusted OAuth applications.
• ghe-check-disk-usage incorrectly defaulted to a --verbose run.
• When migrating from GitHub.com or another GitHub Enterprise appliance, an @ could cause comments to be truncated.
• Administrators couldn't restore deleted LFS objects.
• Pull request review comment webhooks could fail to send.
• When a SAML user whose normalized username matches an organization's name tried to authenticate, the organization's attributes such as profile email could be incorrecty altered.
• A configuration run could revert an SSL certificate to an automatically generated self-signed certificate.
• Graphs in the Management Console monitoring page were incorrectly sorted.

Upcoming deprecation of GitHub Enterprise 2.6

GitHub Enterprise 2.6 will be deprecated as of April 26, 2017. 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 as soon as possible.

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.
• Enqueued background jobs are sometimes not purged when a repository is deleted.
• 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. (updated 2017-03-30)
• An issue or pull request comment containing the string "User-Agent: GitHub-Hookshot" incorrectly triggers a firewall rule and causes an internal server error on several pages, including the author's profile page. (updated 2017-04-05)
• collectd metric paths can be truncated, which causes multiple write attempts to the same file for different metrics. (updated 2017-07-10)
• After changing the visibility of a repository, wiki search results have a conflicting number of displayed search results. Administrators can reindex the wiki through the site admin dashboard. (updated 2017-11-09)

Thanks!

The GitHub Team