Skip to main content
Enterprise Server 3.0
English
� 
Enterprise administrators
Enterprise Server 3.0
English

� 

This version of GitHub Enterprise was discontinued on 2022-02-16. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Enterprise Server 3.0 release notes

Enterprise Server 3.0.25

Download GitHub Enterprise Server 3.0.25

February 17, 2022

📣 This is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

    Security fixes

  • Packages have been updated to the latest security versions.

    Known issues

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

  • Custom firewall rules are removed during the upgrade process.

  • 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 blob's file path is longer than 255 characters.

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

  • When a replica node is offline in a high availability configuration, GitHub Enterprise Server may still route GitHub Pages requests to the offline node, reducing the availability of GitHub Pages for users.

  • Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.

Enterprise Server 3.0.24

Download GitHub Enterprise Server 3.0.24

February 01, 2022

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

    Security fixes

  • Packages have been updated to the latest security versions.

    Bug fixes

  • Pages would become unavailable following a MySQL secret rotation until nginx was manually restarted.

  • When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.

  • The version number would not be correctly updated after a installing a hotpatch using ghe-cluster-each.

  • Spurious error messages concerning the cloud-config.service would be output to the console.

  • When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.

    Changes

  • The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.

    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 removed during the upgrade process.

  • 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 blob's file path is longer than 255 characters.

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

  • When a replica node is offline in a high availability configuration, GitHub Enterprise Server may still route GitHub Pages requests to the offline node, reducing the availability of GitHub Pages for users.

  • Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.

Enterprise Server 3.0.23

Download GitHub Enterprise Server 3.0.23

January 18, 2022

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

    Security fixes

  • Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.

  • Sanitize more secrets in the generated support bundles

  • Packages have been updated to the latest security versions.

    Bug fixes

  • Running ghe-config-apply could sometimes fail because of permission issues in /data/user/tmp/pages.

  • The save button in management console was unreachable by scrolling in lower resolution browsers.

  • IOPS and Storage Traffic monitoring graphs were not updating after collectd version upgrade.

  • Some webhook related jobs could generated large amount of logs.