The 2.11 series release notes contain important changes in this release series.
Downloads Have Been Disabled
This release has been withdrawn and is no longer available. Please upgrade to a newer version or contact support for assistance.
If you have already upgraded your appliance to GitHub Enterprise 2.11.1, please contact support for assistance.
- The 2.11.1 patch release has been withdrawn due to the introduction of a major bug which caused memory budgets for services to be under-allocated. If you have already upgraded your appliance to GitHub Enterprise 2.11.1, please contact support for assistance. (updated 2017-09-21)
- Packages have been updated to the latest security versions.
- LOW: A PDF with looping xref tables caused the PDF renderer to consume high amounts of CPU or hang a user's browser. This vulnerability was also patched in 2.11.0.
- Elasticsearch could exceed recommended heap size. The memory budget is capped at a maximum of 32 GB.
- Upgrading a high availability environment from a 2.10 release to 2.11.0 failed with a
Failed drop elasticsearch scan file error.
- Users had a missing dashboard (i.e. default authenticated homepage) if they didn't own or have direct collaboration permissions to any repositories.
- The repository owner was not displayed when configuring a pre-receive hook.
- Querying the Teams API with an invalid ID failed with a '500 Internal Server Error'.
- Outside collaborators were not added to a repository if mapped to a suspended user during the migration of a repository using
- 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.
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 with through the web interface are incorrectly added directly to the repository.
- GitHub Enterprise clustering can not be configured without https.
- 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.
Hotpatch upgrades from 2.11.0 to 2.11.1 and configuration updates could fail reloading the babeld service. If the upgrade or configuration update fails, run the following command from the affected appliance(s): (updated 2017-09-21)
$ sudo systemctl restart babeld
For a user or organization named
apps, the profile page at
/apps shows an integrations landing page and repository pages at
/apps/<repository> result in a
404 Not Found response due to a conflict with an internal URL. (updated 2017-10-24)
- Changing the parent of a nested team can result in the nested team not receiving updated inherited permissions. (updated 2017-10-27)
- After changing the visibility of a repository, wiki search results have a conflicting number of displayed search results. Administrators can reindex the wiki through the site admin dashboard. (updated 2017-11-09)
- After changing HTTP proxy configuration in the Management Console, webhooks do not use the settings unless
hookshot-resqued is restarted manually via SSH by running:
sudo systemctl restart hookshot-resqued. (updated 2017-12-19)
- The merge button could get stuck in the "Checking for ability to merge" state. (updated 2017-12-20)
- Rebuilding a search index—including during an upgrade to this version—could cause many exceptions to be logged to
/var/log/github/exceptions.log. The fast growth of this log file could cause the root disk to fill up. (updated 2017-12-20)
- Pull request review comments migrated with
ghe-migrator are displayed in the wrong order. (updated 2017-12-20)
- The pull request review request has users reversed, after migration with
ghe-migrator. (updated 2017-12-20)
- The comment count in the "Conversation" tab of a pull request migrated with
ghe-migrator can be wrong. (updated 2017-12-20)
- The create team API endpoint returns a 500 error if LDAP Sync is enabled and the team already exists. (updated 2018-01-09)
gpgverify service may consume large amounts of CPU time even when not processing requests. (updated 2018-02-14)
- Pull request reviewer usernames were not updated if a reviewer was mapped to a different username when migrating repositories using
ghe-migrator. (updated 2018-04-12)
- 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 GitHub Team