GitHub Enterprise - The best way to build and ship software
Features Case Studies Pricing Resources Contact Sign in Try it for free Release notes for the 2.7 series GitHub Enterprise 2.7.21 August 01, 2017 Download Security Fixes Packages have been updated to the latest security versions. CRITICAL : Pages and Git have been updated to handle maliciously constructed ssh:// URLs during submodule cloning . This mitigates the vulnerability detailed in CVE-2017-100117 which could have allowed an authenticated attacker to run arbitrary commands on a GitHub Enterprise environment through Pages builds. (updated 2017-08-10) Bug Fixes Pre-receive hooks with spaces in their paths failed to run.
Deprecation of GitHub Enterprise 2.7 GitHub Enterprise 2.7 is now deprecated as of August 3, 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. 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. Thanks! The GitHub Team GitHub Enterprise 2.7.20 July 12, 2017 Download Security Fixes Packages have been updated to their latest security versions. LOW: OAuth application access tokens and personal access tokens weren't sanitized from support bundles. Bug Fixes collectd metric paths could be truncated, which caused multiple write attempts to the same file for different metrics.
Password reset emails incorrectly displayed reset links were valid for 24 hours when they are only valid for three hours. Pre-receive hooks could not be updated after moving to a new GitHub Enterprise instance, for example after failing over to a replica. Fetches or pushes that transferred more than 2 GB of data were incorrectly recorded as much larger in the logs for the Git proxy service, babeld . Users could receive a temporary "bad pack header" error when fetching a very large repository if the repository was being repacked at the same time.
Changes The ghe-support-bundle command now honors the http_proxy environment variable. 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. 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. Creating a support bundle fails with a “File exists” error if HAproxy logs have been rotated. (updated 2017-07-24) Thanks!
The GitHub Team GitHub Enterprise 2.7.19 June 20, 2017 Download Security Fixes Packages have been updated to their latest security versions. LOW : Tokens were contained in support bundles when they were used in GET requests as a URL parameter. Bug Fixes On a 404 page with an appliance configured to use public mode and SAML, the "Sign in" button was illegible. contributions_backfill background jobs were enqueued on every additional push to a repository, even if it contained no commits from users of the appliance.
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. 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. 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 GitHub Enterprise 2.7.18 May 30, 2017 Download Security Fixes Packages have been updated to the latest security versions. Bug Fixes After the parent repository has been deleted, the Git LFS objects from the forks were inaccessible. Adding a user as a collaborator via the API incorrectly sent an invitation without adding the user. Graphs in the Management Console displayed the sum instead of an average value.
As a result, graphs had incorrectly displayed an increasing metric over time. ghe-upgrade.log contained harmless /proc/... No such file or directory messages. 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. Deleting a search index doesn't delete all associated metadata, which are then incorrectly reused if a new search index is crea
The rest of this page is on the live site.