- Users can create draft pull requests.
- Pull request reviewers can expand and contract the diff view.
- Code authors can commit a batch of suggested changes as a single commit.
- Security alerts are available to customers utilizing GitHub Connect.
- Organization owners can view and export a list of users that have access to a repository.
- Users can create and manage their own project boards.
- Users can set a status on their profile.
- GitHub Enterprise Server supports more AWS EC2 instance types with the AWS Nitro System.
- Organization owners can revoke personal access token via the API.
- Users can view a list of all the repository releases that are being watched.
- Organization owners can restrict members' ability to create teams.
- Users can view all of their subscriptions to issues and pull requests.
- Audit log data is now stored in MySQL instead of Elasticsearch.
- Users can exclude labels from search in an issue or pull request list filter.
- Organization owners can grant users the ability to manage either individual GitHub Apps or all GitHub Apps in an organization.
- Users can mark previously viewed notifications as unread.
- License usage can be uploaded to GitHub Enterprise Cloud for customers utilizing GitHub Connect.
- Users can view information about the author of an issue or pull request by hovering over their username in sticky conversation headers.
- Users can reset their profile picture to the default identicon.
- Pull request review summary comments now support reactions, edit history, quote replies, and copying URLs.
- Organization admins can restrict email notifications for activity within their organization to one or more verified domains.
- Users can pin gists to their profile.
- Organization admins can enable the dependency graph for their organization if utilizing GitHub Connect.
- Users can re-request a code review to notify requested reviewers that changes have been made to a pull request.
- Users can select a different repository when opening a new issue from a comment.
- Users can copy comment permalinks on mobile.
- GitHub Enterprise Server admins can enable Transport Layer Security (TLS) version 1.3.
- Users can close or open an issue or pull request from the projects side pane.
- HIGH: An endpoint in the GitHub API would disclose sensitive user information in its error response. The disclosed information included authentication tokens that could be used to authenticate as unauthorized users. An authenticated user on the instance would be required to access to the affected API.
- LOW: External collaborators received security vulnerability alerts after write access to a repository was revoked.
- LOW: Assigned issues in another users private repository could appear in an issues search.
- Packages have been updated to the latest security versions.
/var/log/github/exceptions.log file could include a large number of
- Organizations imported with
ghe-migrator were not added to the global enterprise account.
- The diff context for diffs that included submodules would sometimes load incorrect content.
- 'Business Account' has been renamed to 'Enterprise Account'.
- The user/organization dashboard is now full-width and responsive.
- When a user opens a new issue from a comment, the new issue will include the full original comment text in its body.
- Users can close the detail pane for a project board by pressing the
- Organization names can now include spaces.
- The blob editor page is now responsive.
- The maximum number of files in API diffs is 3000.
- Organization admins can view the Two-Factor Authentication (2FA) status of organization members via the API.
- Deleted repositories can be restored in bulk.
- Users must have at least one verified email to create a gist.
- If contribution guidelines have been added to a repository, they are shown in the sidebar when a user opens their first issue in that repository.
- Organization administrators can invite members of other organizations in the same business when there are no remaining seats.
- The live page updates keep-alive has been reduced to 30 seconds to better accommodate load balancer related timeouts.
- The minimum recommended hardware requirements for GitHub Enterprise Server have been updated. (updated 2019-05-30)
Backups and Disaster Recovery
GitHub Enterprise Server 2.17 requires at least GitHub Enterprise Backup Utilities 2.17.0 for Backups and Disaster Recovery.
Upcoming deprecation of GitHub Enterprise Server 2.14
GitHub Enterprise Server 2.14 will be deprecated as of July 12, 2019. 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 Server as soon as possible.
Deprecation of GitHub Services
Starting with GitHub Enterprise Server 2.17.0, support for GitHub Services is now deprecated and administrators will not be able to install or configure new GitHub Services. Existing GitHub Services from a previous version of GitHub Enterprise Server will continue to function but GitHub Enterprise Server will not be providing any security or bug fixes to the GitHub Services functionality. At this time, there will be no changes to the existing functionality, but a warning banner is displayed with the deprecation announcement blog post. Administrators can see which repositories are using GitHub Services with
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
- Custom firewall rules aren't maintained during an upgrade.
- Subversion (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.
- Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
- Resque workers may not be cleaned up following a configuration run leading to a growing number of stale workers which in turn could lead to high memory consumption.
- Adding a new node to a currently or previously configured high availability replication primary node that has been upgraded to GitHub Enterprise Server 2.17 may fail due to a missing
/etc/openvpn/easy-rsa/openssl.cnf file. (updated: 2019-06-19)
- Hypervisor type and root volumes are incorrectly detected on AWS Nitro instance types, preventing non-hotpatch upgrades. (updated: 2019-07-09)
- Lines in gists are not selectable. (updated: 2019-07-19)
The GitHub Team