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

Security Fixes

• Ubuntu kernel and packages have been updated to the latest security versions.
• HIGH: Update HAProxy to address CVE-2015-3281, which could allow an attacker to use a specially crafted request to read memory contents that might contain data from a past request or session.
• MEDIUM: Scopeless access tokens could list private Gists.
• LOW: Service hooks could log passwords used for HTTP Basic authentication to disk. (updated 2015-07-28)
• This release and previous releases of GitHub Enterprise are not affected by the OpenSSL Advisory issued 9 July 2015 (CVE-2015-1793)

Bug Fixes

• Ubuntu kernel and packages have been updated to the latest bugfix versions.
• A repository could be incorrectly deleted from disk after migration to the new repository layout. If a repository was deleted and no other repositories were created before a reboot, we reused the ID of the deleted repository. This happens because when MySQL starts, the auto increment ID system is inititialized with the last ID in the table. This means the first new repository created would have the same ID as the deleted repository, and the repository cleanup job would incorrectly see the new repository as deleted.
• The Redis appendonly file could become corrupt when performing a hard reboot of the appliance, which caused Redis to not start.
• A race condition in the pull request synchronize event could result in incorrect SHAs and timestamps in the webhook payload.
• Collectd could cause lots of tiny writes to the root volume, which could affect the performance of the appliance.
• Old webhook delivery logs were deleted inefficiently. We've changed the directory structure so we can delete them more efficiently.
• Viewing compare pages and pull requests could result in a 500 error due to a race condition.
• LDAP restricted groups couldn't be removed.
• The site admin showed Gravatar icons for users' additional email addresses.
• SNMP couldn't be run on high availability replicas.
• A high availability replica that's been promoted to primary and then set up as a replica again didn't properly show the replica status page, but showed 'Starting...' instead.
• Searching Gists could fail after upgrading to GitHub Enterprise 2.2.
• It was not possible to view user profiles or repositories for users with usernames that started with "raw".
• Events in the github_audit and haproxy log streams were being logged twice.
• Setting up high availability replication could fail due to a large entry in one of the MySQL tables.
• Promoting a high availability replica could fail if Elasticsearch took too long to restart.

Changes

• We've added a graph for disk utilization to the monitoring dashboard.
• Direct root SSH access was not possible in the past, but as an additional measure we've also added PermitRootLogin to no within the SSH configuration.
• We've added support for the C4 and M4 AWS instance types.
• You are now prompted to confirm that you wish high availability replication to continue when we detect you are attempting to setup replication on an instance that is currently, or has been, an active configured instance. This reduces the chances of accidental replication over an active primary instance.
• The diagnostics output gathered on high availability replicas now only gathers information relevant to replica instances.
• NTP is now configured on the high availability replica when replication is setup.
• Old compressed rotated log files are no longer retained during an upgrade.

Known Issues

• 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.

• Organization invitation emails are sent from the configured support email address rather than the no-reply address.

• We can fail to properly create the key for the secure connection between a high availability replica and the primary, which causes replication setup to fail.

• Management console sessions can expire too quickly for Safari users.

• Gist repositories are not garbage collected by the maintenance scheduler.

• Gist profile pages don't have proper styling when subdomain isolation is disabled.

• Custom firewall rules aren't maintained during an upgrade.

• Dashboard activity feed links point to wrong hostname after restoring from backup if the hostname has changed.

• On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.

• Jobs stuck on code indexing can delay other jobs from running.

• Replication setup fails for IPv6 hosts.

• The management console settings interface doesn't clearly show if you have previously uploaded certificate files or a private key.

• Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes.

• The site admin shows errors in the 'repo reflogs' section, which isn't fully implemented on GitHub Enterprise.

• Gists can't be created when using Safari 8.x in Private Mode.

• Deleting a user doesn't delete their gists, which can cause problems with replication.

• In our instructions to merge a pull request on the command line, we show the steps to merge using the Git protocol even when private mode is on. Private mode forces authentication but the Git protocol is unauthenticated so the steps will always fail. We also don't show the steps to merge using SSH.

• We incorrectly redirect to the dashboard if you access 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.

• We display the time in the scheduled maintenance banner in UTC instead of the viewer's timezone.

• Users with LDAP DNs longer than 255 characters are suspended if LDAP Sync is enabled.

• Services fail to start properly after upgrading to this release if SSL is disabled. (updated 2015-07-20)

• Using uppercase characters in the hostname causes a redirect loop. (updated 2015-07-28)

• When a fork is detached from its repository network by an administrator or by changing visibility, its filesystem path won't be updated on a high availability replica until at least one commit has been pushed. (updated 2015-08-13)

• Updates to Wiki pages by users without a primary email address set throw errors. (updated 2015-08-25)

• 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 'repo reflogs' section of the site admin was removed in 2.2.4.

Thanks!

The GitHub Team