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

Git client vulnerabilities

A number of critical Git security vulnerabilities were recently announced that affect all versions of the official Git client.

We strongly recommend that you ensure that all users update their Git clients, in addition to upgrading to this GitHub Enterprise release.

More details on these vulnerabilities can be found in the official announcement, and the associated CVEs, CVE-2018-11233 and CVE-2018-11235. (updated 2018-05-30)

Security Fixes

• CRITICAL There was a remote code execution vulnerability that leveraged CVE-2018-11235 during the Pages build process. The Git package has been updated to address the vulnerability in the Pages build process. This fix is also available in GitHub Enterprise 2.13.2. (updated 2018-05-30)
• Packages have been updated to the latest security versions.

Bug Fixes

• The Management Console contained broken links to help documentation.
• Maintenance mode could be unset while a configuration run was in progress.
• Viewing a team discussion showed a "You can't perform that action at this time" error at the top of the page.
• A background job that purges deleted storage objects could cause backups to fail if run whilst a backup was in progress.
• Restoring a backup to an unconfigured GitHub Enterprise appliance could fail to restore Pages data with a "could not find 3 online voting fileservers" error.
• Updating branch protections from the API ignored the restricted teams parameter.
• Exporting a repository didn't include project boards.
• Performing bulk actions, like labelling, on pull requests would silently fail if issues were disabled.

Changes

• Add a notice for the upcoming GitHub services deprecation.
• Admins can see which repositories are using GitHub Services with ghe-legacy-github-services-report.
• Improve Git rate limit configuration to prevent over-limiting of Git operations.

Known Issues

• 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.
• 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.
• Pull request review comments are missing from an import with ghe-migrator.
• Nameid-format matching on SAML response is too strict when value is "unspecified", which can cause an error with the "Another user already owns the account." message if the IdP changes NameID. (updated 2018-06-25)
• The import of protected branches with ghe-migrator fails when the creator of the protected branch no longer exists on the source instance. (updated 2018-10-31)
• The import of project boards with ghe-migrator fails when the creator of a card on the board no longer exists on the source instance. (updated 2018-11-21)

Thanks!

The GitHub Team