Due to a database migration error, we have disabled access to the 2.19.0 images. This error will be resolved in the next patch release.
- Organization and repository administrators can assign the
maintain roles to users and teams.
- When an issue is referenced with a closing keyword in a pull request description, the referenced issue will now surface the relevant pull request information in its header.
- The dependency graph supports
.fsproj files that list NuGet dependencies in their PackageReference section.
- The WebAuthn standard is supported for authentication.
- Users can change the project board columns of issues directly from the issue sidebar.
- GitHub Pages supports adding a remote theme using Jekyll.
- Administrators can utilize the Audit Log GraphQL API.
- The dependency graph supports scoped npm packages.
- Repositories can be set to delete the head branch of a pull request once it has merged into the base branch.
- Enterprise accounts can be managed using the GraphQL API.
- Enterprise accounts can issue their members SSH certificates to access repositories over Git.
- Administrators can enable autolink references on repositories. (updated 2019-11-13)
- Packages have been updated to the latest security versions.
- Team maintainers could not add child teams to their teams if "Allow members to create teams" was disabled.
- Pull requests authors with read permissions could not re-request reviews.
- A label could be shown as removed from a pull request that it was never added to.
- The web notification retention policy has been increased to 5 months for all notification types.
ghe-repl-status command shows more granular status information for consul replication.
- Audit log data is now stored in Elasticsearch instead of MySQL.
- Users will only be able to see the Secret teams they are part of in the list of teams.
- Users will be listed as owners of the organizations they own when logged in.
- Pull requests are shown under Recent Activity when they've recently been reviewed.
Backups and Disaster Recovery
GitHub Enterprise Server 2.19 requires at least GitHub Enterprise Backup Utilities 2.19.0 for Backups and Disaster Recovery.
Upcoming Deprecation of GitHub Enterprise Server 2.16
GitHub Enterprise Server 2.16 will be deprecated as of January 22, 2020. 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.
Upcoming Deprecation of Adding New SSH-DSS Keys
The addition of new SSH-DSS keys will be removed in GitHub Enterprise Server 2.20.0.
Upcoming Deprecation of the Legacy Gravatar Service
Support for using an external service for Avatars was deprecated in GitHub Enterprise Server 2.1.0. At the time, functionality was implemented to copy avatars from the external service to the GitHub Enterprise Server and the configuration options remained in Enterprise Manage for instances configured with an external service prior to the deprecation. This functionality and configuration will be removed from GitHub Enterprise Server 2.20.0.
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
- Custom firewall rules are not maintained during an upgrade.
- 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.
- The Let's Encrypt certificate registration feature consistently fails following an update to the external API.
- When pushing to a gist, an exception could be triggered during the post-receive hook.
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23)
The GitHub Team