The 2.4 series release notes contain important changes in this release series.

Bug Fixes

• The high availability replication status as reported by ghe-repl-status would not report a failure if ElasticSearch was not running.
• The temporary support bundle archive wasn't removed after a successful upload.
• ghe-upgrade would fail with a GPG signature error if run as the root user.
• High availability replication sometimes failed to set the MySQL password correctly which prevented MySQL replication from starting.
• Non-push events for Organization webhooks failed to be recorded in the 'Recent Deliveries' list.
• A configuration option in the /etc/ssh/sshd_config file contained an equals sign which caused cloud-init user data scripts to fail.
• Migrating user, organization, and repository data using ghe-migrator could fail to import a migration archive if it contained empty records.
• Migrating user, organization, and repository data using ghe-migrator could fail to set the team maintainer role on the destination team during the import.
• Log forwarding did not include the GitHub application's Nginx log.
• The tokens added to gist raw links in private mode expired in 30 seconds. These now expire after a week.
• The merge button could remain disabled on pull requests with protected branches and required statuses when all Travis-initiated status checks had passed.
• Pages URLs without a trailing slash redirected incorrectly.
• The default branch selector within the repository settings didn't correctly search for branches.
• Adding a second unnamed file to a gist would overwrite the first unnamed file added to that gist.

Changes

• ghe-support-bundle can now be used to upload arbitrary files directly to GitHub using a new -f path option.
• Admin Tools now shows whether protected branch status checks are enforced for admin users or not.

Security Fixes

• MED OpenJDK has been updated to address multiple vulnerabilities related to information disclosure, data integrity and availability.
• MED NTP packages have been updated to address multiple vulnerabilities.
• Packages have been updated to the latest security versions.

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.
• The management console settings interface doesn't clearly show if you have previously uploaded certificate files or a private key.
• Management console sessions can expire too quickly for Safari users.
• Custom firewall rules aren't maintained during an upgrade.
• Repositories that are in an incomplete state, which is a rare problem, can cause the migration to the new repository disk layout to fail.
• Enqueued background jobs are sometimes not purged when a repository is deleted.
• Restoring backups from previous versions fail. As a workaround, create an instance matching the version the backup was taken from, restore the backup, then upgrade. (updated 2015-11-05)
• High availability replication sometimes fails to set the correct master identifier during an upgrade. This prevents MySQL replication from starting. (updated 2015-11-11)
• Viewing raw files in repositories owned by a user or organization named "github" fails with a 400 error. (updated 2015-12-15)
• Trying to add a file to a repository with Subversion 1.9 clients incorrectly detects the file already exists and fails. (updated 2016-01-14)

Errata

• The failure to migrate repositories in an incomplete state to the new repository disk layout was resolved in 2.4.0. (updated 2015-12-01)

Thanks!

The GitHub Team