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

Security Fixes

• Packages have been updated to the latest security versions.

Bug Fixes

• Background jobs were deleted and lost when stopping replication. This happens when failing over to a high availability replica and during a cluster configuration run.
• Webhook delivery logs were not accessible and logged when a proxy was configured.
• It was possible to change the parent repository to itself.
• SVN checkout failed if a repository has symlinks.
• Running git symbolic-ref would hang when resolving references with broken symlinks.
• LDAP Sync suspended users that were already suspended, causing unnecessary audit log entries.
• Changing the default branch of a repository was not synchronized to a high availability replica, so the wrong branch was set as default after fail over.
• Webhook delivery logs were not pruned causing unnecessary storage usage.
• Webhook delivery logs may not be accessible and logged if the first webhook event for the day was a push event.
• Custom messaging for suspended users was not displayed to suspended SAML users.
• LDAP Sync removed and re-added users or teams when their distinguished name contained upper case characters.
• Forking a repository could fail if the maintenance job for the repository's network ran at the same time.
• After restarting a crashed process, writing data to the management console monitoring graphs may not have immediately restarted.
• An error was thrown when trying to access audit logs containing authentication attempts using two-factor authentication.
• In a clustering environment, the web application service could fail to start after cluster configuration run.
• Upgrade to 2.7.4 failed on Running Migration if there were multiple OAuth applications named GitHub Desktop.

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.
• 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. (updated 2017-02-23)
• Git LFS objects may take up to an hour to replicate in a High Availability configuration. (updated 2017-02-23)
• 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