The 2.19 series release notes contain important changes in this release series.
Due to a database migration error, we have disabled access to the 2.19.1 images. This error will be resolved in the next patch release.
Security Fixes
- LOW: The
script-src: 'unsafe-inline'
CSP header was applied to all paths for Enterprise Manager.
- Packages have been updated to the latest security versions.
Bug Fixes
- Promoting a replica in an active HA environment could fail to properly apply configuration changes and remove a pre-flight check holding page.
- In certain cluster configurations, background jobs are unable to communicate with local storage services.
- Upgrading from 2.17 to 2.19 could fail with a database migration error.
Changes
- The Google Accounts Daemon and
google_set_hostname
DHCP hook are now disabled on Google Cloud Platform images.
- GitHub Enterprise Server is now available in the eu-north-1 AWS region.
Known Issues
- 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)
Thanks!
The GitHub Team