Skip to content

Commit b99d0cf

Browse files
release-controller[bot]Release-Controllerdooleydevinrachaelrenkvgrl
authored
Patch release notes for GitHub Enterprise Server (#54942)
Co-authored-by: Release-Controller <[email protected]> Co-authored-by: Devin Dooley <[email protected]> Co-authored-by: Rachael Rose Renk <[email protected]> Co-authored-by: Vanessa <[email protected]>
1 parent 16ef992 commit b99d0cf

File tree

5 files changed

+266
-0
lines changed

5 files changed

+266
-0
lines changed

‎data/release-notes/enterprise-server/3-12/17.yml‎

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
date: '2025-03-25'
2+
sections:
3+
security_fixes:
4+
- |
5+
Packages have been updated to the latest security versions.
6+
bugs:
7+
- |
8+
The `ghe-upgrade` command returned a zero exit code despite encountering errors.
9+
- |
10+
Restoring from a backup did not always apply the latest data from GitHub Actions. All GitHub Actions data is now restored with a backup.
11+
- |
12+
Users could not use the `/manage/v1/config/apply` API endpoint to trigger the first configuration run on an instance.
13+
changes:
14+
- |
15+
Update the bundled `actions/setup-dotnet` with the latest versions from https://github.com/actions/setup-dotnet.
16+
known_issues:
17+
- |
18+
Custom firewall rules are removed during the upgrade process.
19+
- |
20+
During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
21+
- |
22+
If the root site administrator is locked out of the Management Console after failed login attempts, the account does not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
23+
- |
24+
The `mbind: Operation not permitted` error in the `/var/log/mysql/mysql.err` file can be ignored. MySQL 8 does not gracefully handle when the `CAP_SYS_NICE` capability isn't required, and outputs an error instead of a warning.
25+
- |
26+
On an instance with the HTTP `X-Forwarded-For` header configured for use behind a load balancer, all client IP addresses in the instance's audit log erroneously appear as 127.0.0.1.
27+
- |
28+
{% data reusables.release-notes.large-adoc-files-issue %}
29+
- |
30+
The `reply.[hostname]` subdomain is falsely always displaying as having no ssl and dns record, when testing the domain settings via management console **without subdomain isolation**. When regenerating the certificates with management console, the `subdomain reply.[hostname]` is missing from the ssl certification.
31+
- |
32+
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
33+
- |
34+
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %}
35+
- |
36+
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
37+
- |
38+
Some customers upgrading from 3.11.x or 3.12.x may experience a bug with the feature "Automatic update checks", filling the root disk with logs causing a system degradation. To prevent this, you can turn off the feature "[Enable automatic update check](/admin/upgrading-your-instance/preparing-to-upgrade/enabling-automatic-update-checks#enabling-automatic-update-checks)" in the management console.
39+
- |
40+
After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows.

‎data/release-notes/enterprise-server/3-13/13.yml‎

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
date: '2025-03-25'
2+
sections:
3+
security_fixes:
4+
- |
5+
Packages have been updated to the latest security versions.
6+
bugs:
7+
- |
8+
The `ghe-upgrade` command returned a zero exit code despite encountering errors.
9+
- |
10+
When performing an upgrade with an upgrade package, the process did not terminate when an invalid target partition was provided with the `-t` flag.
11+
- |
12+
Users could not use the `/manage/v1/config/apply` API endpoint to trigger the first configuration run on an instance.
13+
- |
14+
Restoring from a backup did not always apply the latest data from GitHub Actions. All GitHub Actions data is now restored with a backup.
15+
- |
16+
For instances in a high availability configuration, Elasticsearch indices were deleted on failover and when `ghe-repl-teardown REPLICA_HOSTNAME` was run from the primary instance. All indices are recoverable except audit log indices, whose source of truth is Elasticsearch itself.
17+
- |
18+
In Azure environments, running `ghe-single-config-apply` or `ghe-repl-setup` resulted in "Permission denied" errors during the pre-flight check.
19+
changes:
20+
- |
21+
Elasticsearch shards are excluded from the replica node when stopping replication via `ghe-repl-stop`. To prevent Elasticsearch from being stopped before all shards have been removed, Elasticsearch is polled until the shard count on the replica node is zero instead of waiting for a maximum timeout of 30 seconds.
22+
- |
23+
Update the bundled `actions/setup-dotnet` with the latest versions from https://github.com/actions/setup-dotnet.
24+
known_issues:
25+
- |
26+
During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
27+
- |
28+
If the root site administrator is locked out of the Management Console after failed login attempts, the account does not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
29+
- |
30+
On an instance with the HTTP `X-Forwarded-For` header configured for use behind a load balancer, all client IP addresses in the instance's audit log erroneously appear as 127.0.0.1.
31+
- |
32+
For an instance in a cluster configuration and with GitHub Actions enabled, restoring a cluster from backup requires targeting the primary DB node.
33+
- |
34+
When following the steps for [Replacing the primary MySQL node](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-the-primary-mysql-node), step 14 (running `ghe-cluster-config-apply`) might fail with errors. If this occurs, re-running `ghe-cluster-config-apply` is expected to succeed.
35+
- |
36+
Running a config apply as part of the steps for [Replacing a node in an emergency](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-a-node-in-an-emergency) may fail with errors if the node being replaced is still reachable. If this occurs, shutdown the node and repeat the steps.
37+
- |
38+
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %}
39+
- |
40+
When restoring data originally backed up from a 3.13 or greater appliance version, the Elasticsearch indices need to be reindexed before some of the data will show up. This happens via a nightly scheduled job. It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`.
41+
- |
42+
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
43+
- |
44+
After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance.
45+
- |
46+
After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows.

‎data/release-notes/enterprise-server/3-14/10.yml‎

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
date: '2025-03-25'
2+
sections:
3+
security_fixes:
4+
- |
5+
Packages have been updated to the latest security versions.
6+
bugs:
7+
- |
8+
The `ghe-upgrade` command returned a zero exit code despite encountering errors.
9+
- |
10+
When performing an upgrade with an upgrade package, the process did not terminate when an invalid target partition was provided with the `-t` flag.
11+
- |
12+
Users could not use the `/manage/v1/config/apply` API endpoint to trigger the first configuration run on an instance.
13+
- |
14+
For instances in a high availability configuration, Elasticsearch indices were deleted on failover and when `ghe-repl-teardown REPLICA_HOSTNAME` was run from the primary instance. All indices are recoverable except audit log indices, whose source of truth is Elasticsearch itself.
15+
- |
16+
Restoring from a backup did not always apply the latest data from GitHub Actions. All GitHub Actions data is now restored with a backup.
17+
- |
18+
In Azure environments, running `ghe-single-config-apply` or `ghe-repl-setup` resulted in "Permission denied" errors during the pre-flight check.
19+
- |
20+
On instances with a GitHub Advanced Security license, some secret scanning alerts were opened incorrectly despite the relevant folders or files being excluded from secret scanning.
21+
changes:
22+
- |
23+
Elasticsearch shards are excluded from the replica node when stopping replication via `ghe-repl-stop`. To prevent Elasticsearch from being stopped before all shards have been removed, Elasticsearch is polled until the shard count on the replica node is zero instead of waiting for a maximum timeout of 30 seconds.
24+
- |
25+
Update the bundled `actions/setup-dotnet` with the latest versions from https://github.com/actions/setup-dotnet.
26+
known_issues:
27+
- |
28+
During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
29+
- |
30+
If the root site administrator is locked out of the Management Console after failed login attempts, the account does not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
31+
- |
32+
On an instance with the HTTP `X-Forwarded-For` header configured for use behind a load balancer, all client IP addresses in the instance's audit log erroneously appear as 127.0.0.1.
33+
- |
34+
{% data reusables.release-notes.large-adoc-files-issue %}
35+
- |
36+
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
37+
- |
38+
When following the steps for [Replacing the primary MySQL node](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-the-primary-mysql-node), step 14 (running `ghe-cluster-config-apply`) might fail with errors. If this occurs, re-running `ghe-cluster-config-apply` is expected to succeed.
39+
- |
40+
Running a config apply as part of the steps for [Replacing a node in an emergency](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-a-node-in-an-emergency) may fail with errors if the node being replaced is still reachable. If this occurs, shutdown the node and repeat the steps.
41+
- |
42+
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %}
43+
- |
44+
When restoring data originally backed up from a 3.13 or greater appliance version, the Elasticsearch indices need to be reindexed before some of the data will show up. This happens via a nightly scheduled job. It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`.
45+
- |
46+
An organization-level code scanning configuration page is displayed on instances that do not use GitHub Advanced Security or code scanning.
47+
- |
48+
In the header bar displayed to site administrators, some icons are not available.
49+
- |
50+
When enabling automatic update checks for the first time in the Management Console, the status is not dynamically reflected until the "Updates" page is reloaded.
51+
- |
52+
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
53+
- |
54+
After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance.
55+
- |
56+
After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows.

‎data/release-notes/enterprise-server/3-15/5.yml‎

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
date: '2025-03-25'
2+
sections:
3+
security_fixes:
4+
- |
5+
Packages have been updated to the latest security versions.
6+
bugs:
7+
- |
8+
In Azure environments, running `ghe-single-config-apply` or `ghe-repl-setup` resulted in "Permission denied" errors during the pre-flight check.
9+
- |
10+
The `ghe-upgrade` command returned a zero exit code despite encountering errors.
11+
- |
12+
When performing an upgrade with an upgrade package, the process did not terminate when an invalid target partition was provided with the `-t` flag.
13+
- |
14+
For instances in a high availability configuration, Elasticsearch indices were deleted on failover and when `ghe-repl-teardown REPLICA_HOSTNAME` was run from the primary instance. All indices are recoverable except audit log indices, whose source of truth is Elasticsearch itself.
15+
- |
16+
On instances with a GitHub Advanced Security license, some secret scanning alerts were opened incorrectly despite the relevant folders or files being excluded from secret scanning.
17+
changes:
18+
- |
19+
Elasticsearch shards are excluded from the replica node when stopping replication via `ghe-repl-stop`. To prevent Elasticsearch from being stopped before all shards have been removed, Elasticsearch is polled until the shard count on the replica node is zero instead of waiting for a maximum timeout of 30 seconds.
20+
- |
21+
Update the bundled `actions/setup-dotnet` with the latest versions from https://github.com/actions/setup-dotnet.
22+
known_issues:
23+
- |
24+
During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
25+
- |
26+
If the root site administrator is locked out of the Management Console after failed login attempts, the account does not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
27+
- |
28+
On an instance with the HTTP `X-Forwarded-For` header configured for use behind a load balancer, all client IP addresses in the instance's audit log erroneously appear as 127.0.0.1.
29+
- |
30+
{% data reusables.release-notes.large-adoc-files-issue %}
31+
- |
32+
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
33+
- |
34+
When following the steps for [Replacing the primary MySQL node](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-the-primary-mysql-node), step 14 (running `ghe-cluster-config-apply`) might fail with errors. If this occurs, re-running `ghe-cluster-config-apply` is expected to succeed.
35+
- |
36+
Running a config apply as part of the steps for [Replacing a node in an emergency](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-a-node-in-an-emergency) may fail with errors if the node being replaced is still reachable. If this occurs, shutdown the node and repeat the steps.
37+
- |
38+
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %}
39+
- |
40+
When restoring data originally backed up from a 3.13 or greater appliance version, the Elasticsearch indices need to be reindexed before some of the data will show up. This happens via a nightly scheduled job. It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`.
41+
- |
42+
An organization-level code scanning configuration page is displayed on instances that do not use GitHub Advanced Security or code scanning.
43+
- |
44+
In the header bar displayed to site administrators, some icons are not available.
45+
- |
46+
When enabling automatic update checks for the first time in the Management Console, the status is not dynamically reflected until the "Updates" page is reloaded.
47+
- |
48+
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
49+
- |
50+
When initializing a new GHES cluster, nodes with the `consul-server` role should be added to the cluster before adding additional nodes. Adding all nodes simultaneously creates a race condition between nomad server registration and nomad client registration.
51+
- |
52+
Admins setting up cluster high availability (HA) may encounter a spokes error when running `ghe-cluster-repl-status` if a new organization and repositories are created before using the `ghe-cluster-repl-bootstrap` command. To avoid this issue, complete the cluster HA setup with `ghe-cluster-repl-bootstrap` before creating new organizations and repositories.
53+
- |
54+
After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance.

0 commit comments

Comments
 (0)