The 2.6 series release notes contain important changes in this release series.
- Packages have been updated to the latest security versions.
- In a clustering environment, the web application service could fail to start after cluster configuration run.
- 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.
- Forking a repository could fail if the maintenance job for the repository's network ran at the same time.
git symbolic-ref would hang when resolving references with broken symlinks.
- LDAP Sync suspended users that were already suspended users, 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.
- LDAP Sync removed and re-added users or teams when their distinguished name contained upper case characters.
- 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.
- 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.
- On instances upgraded from 2.3 and earlier, restoring a protected branch archived whilst running 2.3, will not restore all the settings correctly. This does not affect new instances or protected branches archived on later releases.
- Editing custom messages in the Admin Center doesn't provide emoji suggestions.
- Native emoji are lost when saving custom messages in the Admin Center.
- Repository push logs don't record whether a push was forced.
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.
- Uploading PNG images with through the web interface can fail with the error 'Something went really wrong, and we can't process that file.'
- GitHub Enterprise clustering can not be configured without https.
- Console text is difficult to read on OpenStack KVM.
- 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)
The GitHub Team