date: '2022-02-01'
sections:
  security_fixes:
    - Packages have been updated to the latest security versions.
  bugs:
    - 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 {% data variables.product.prodname_ghe_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](https://github.com/blog/2105-upload-files-to-your-repositories) 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, {% data variables.product.product_name %} may still route {% data variables.product.prodname_pages %} requests to the offline node, reducing the availability of {% data variables.product.prodname_pages %} for users.
    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.