The 2.7 series release notes contain important changes in this release series.
- 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.
/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
- Administrators couldn't restore deleted LFS objects.
- 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.
- 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.
- Additional white spacing can sometimes be seen above the Admin center header.
- 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-03-30)
- collectd metric paths can be truncated, which causes multiple write attempts to the same file for different metrics. (updated 2017-07-10)
The GitHub Team