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

Security Fixes

• LOW: An internal upload policies API disclosed which users had push access to a repository.
• LOW: An internal administrative API was vulnerable to cross-site request forgery (CSRF).
• Packages have been updated to the latest security versions.

Bug Fixes

• Git LFS objects could take up to an hour to replicate in a High Availability configuration.
• Pre-receive hooks failed to output UTF-8 characters.
• Migrations failed to preserve a label with a / character.
• A previously configured replica appliance excessively logged errors during High Availability initialization.
• The Management Console Add new SSH key field incorrectly allowed an SSH fingerprint instead of the contents of the key.
• A former primary appliance failed to create or update pre-receive hook environments.
• An updated SAML Verification certificate did not take effect until the github-unicorn service was restarted.

Changes

• The Reactivate suspended users configuration has changed to reflect the current configured state.
• The <Destination> element is no longer optional in the SAML response.

Deprecation of GitHub Enterprise 2.4

GitHub Enterprise 2.4 is now deprecated as of February 9, 2017. That means that no patch releases will be made, even for critical security issues, after this release. For better performance, improved security, and new features, upgrade to the newest version of GitHub Enterprise as soon as possible.

Upcoming deprecation of GitHub Enterprise 2.5

GitHub Enterprise 2.5 will be deprecated as of March 14, 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.
• Additional white spacing can sometimes be seen above the Admin center header.
• Graphs in the Management Console monitoring page are incorrectly sorted.
• The initial import of the VMware OVA image may fail when deployed via vCenter Server 6.0 or 6.5. The import will succeed when performed directly on an ESXi host.
• 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)

Thanks!

The GitHub Team