|
1 | 1 | date: 2021-11-23 |
2 | 2 | sections: |
3 | 3 | security_fixes: |
4 | | - - Packages have been updated to the latest security versions. |
| 4 | + - Packages have been updated to the latest security versions. |
5 | 5 | bugs: |
6 | | - - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. |
7 | | - - Pre-receive hooks would fail due to undefined `PATH`. |
| 6 | + - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. |
| 7 | + - Pre-receive hooks would fail due to undefined `PATH`. |
8 | 8 | - Running `ghe-repl-setup` would return an error "cannot create directory /data/user/elasticsearch: File exists" if the instance had previously been configured as a replica. |
9 | | - - Running `ghe-support-bundle` returned an error `integer expression expected`. |
10 | | - - After setting up a high availability replica, `ghe-repl-status` included an error in the output `unexpected unclosed action in command`. |
11 | | - - In large GHES Cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. |
12 | | - - Some critical services may not have been available on backend nodes in GHES Cluster. |
13 | | - - The repository permissions to the user returned by the `/repos` API would not return the full list. |
14 | | - - The `childTeams` connection on the `Team` object in the GraphQL schema produced incorrect results under some circumstances. |
15 | | - - In a high availability configuration, repository maintenance always showed up as failed in stafftools, even when it succeeded. |
16 | | - - User defined patterns would not detect secrets in files like `package.json` or `yarn.lock`. |
| 9 | + - Running `ghe-support-bundle` returned an error `integer expression expected`. |
| 10 | + - After setting up a high availability replica, `ghe-repl-status` included an error in the output `unexpected unclosed action in command`. |
| 11 | + - In large GHES Cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. |
| 12 | + - Some critical services may not have been available on backend nodes in GHES Cluster. |
| 13 | + - The repository permissions to the user returned by the `/repos` API would not return the full list. |
| 14 | + - The `childTeams` connection on the `Team` object in the GraphQL schema produced incorrect results under some circumstances. |
| 15 | + - In a high availability configuration, repository maintenance always showed up as failed in stafftools, even when it succeeded. |
| 16 | + - User defined patterns would not detect secrets in files like `package.json` or `yarn.lock`. |
17 | 17 | changes: |
18 | | - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. |
19 | | - - Upgrade collectd to latest version 5.12.0. |
20 | | - - We have added extra text to the admin console to remind users about the mobile apps data collection for experience improvement purposes. |
| 18 | + - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. |
| 19 | + - Upgrade collectd to latest version 5.12.0. |
| 20 | + - We have added extra text to the admin console to remind users about the mobile apps data collection for experience improvement purposes. |
21 | 21 | known_issues: |
22 | 22 | - On a freshly set up without any users, an attacker could create the first admin user. |
23 | 23 | - Custom firewall rules are removed during the upgrade process. |
|
0 commit comments