[Release note update]: Invalid Known Issue in release notes (#55239)
Co-authored-by: Vanessa <vgrl@github.com>
This commit is contained in:
Rachael Rose Renk
committed by
GitHub
GitHub
parent
53d1b0b4a6
commit
f5bc3655eb
@@ -190,6 +190,11 @@ sections:
|
||||
Restoring backups with `ghe-restore` on a GHES cluster will exit prematurely if `redis` has not restarted properly.
|
||||
- |
|
||||
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %} [Updated: 2024-06-17]
|
||||
|
||||
bugs:
|
||||
- |
|
||||
Repositories originally imported using `ghe-migrator` did not correctly track GitHub Advanced Security contributions.
|
||||
|
||||
deprecations:
|
||||
- heading: Upgrading GitHub Enterprise Server Backup Utilities using a Git repository is no longer supported
|
||||
notes:
|
||||
@@ -199,3 +204,4 @@ sections:
|
||||
Instead, to upgrade the tool using a compressed archive, download the relevant GitHub Enterprise Server Backup Utilities release from the [Releases](https://github.com/github/backup-utils/releases) page of the `github/backup-utils` repository. For more information, see [AUTOTITLE](/admin/backing-up-and-restoring-your-instance/configuring-backups-on-your-instance#upgrading-github-enterprise-server-backup-utilities).
|
||||
|
||||
This deprecation does not affect the functionality of the GitHub Enterprise Server Backup Utilities tool or your ability to backup or restore your GitHub Enterprise Server instance. [Updated: 2024-03-15]
|
||||
|
||||
|
||||
@@ -40,8 +40,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
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**.
|
||||
- |
|
||||
@@ -50,3 +48,9 @@ sections:
|
||||
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %}
|
||||
- |
|
||||
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.10, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -46,8 +46,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using `ghe-migrator` will not correctly track GitHub Advanced Security contributions.
|
||||
- |
|
||||
The `reply.[HOSTNAME]` subdomain is falsely always displaying as having no SSL and DNS record, when testing the domain settings via the Management Console without subdomain isolation.
|
||||
- |
|
||||
@@ -56,4 +54,10 @@ sections:
|
||||
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %}
|
||||
- |
|
||||
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
|
||||
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.11, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -21,8 +21,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
@@ -35,3 +33,9 @@ sections:
|
||||
Attempting to stop replications after stopping GitHub Actions on a GitHub Enterprise Server instance would fail, reporting that MSSQL was not responding. The can be avoided by start MSSQL prior to stopping replication `/usr/local/share/enterprise/ghe-nomad-jobs queue /etc/nomad-jobs/mssql/mssql.hcl`
|
||||
- |
|
||||
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.
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.12, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -42,8 +42,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
@@ -54,3 +52,9 @@ sections:
|
||||
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
|
||||
- |
|
||||
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.
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.13, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -36,8 +36,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
@@ -48,3 +46,10 @@ sections:
|
||||
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
|
||||
- |
|
||||
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.
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.14, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -44,8 +44,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
@@ -60,3 +58,7 @@ sections:
|
||||
errata:
|
||||
- |
|
||||
The warning and known issues section have been updated to accurately reflect that instances installed on GCP will face issues while hotpatching to 3.12.15. Previously, the warning and known issue indicated that customers would face issues either while upgrading or hotpatching to version 3.12.15. [Updated: 2025-03-11]
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.2, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -70,7 +70,10 @@ sections:
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
{% data reusables.release-notes.2023-12-backup-utils-exit-early-redis %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %} [Updated: 2024-06-17]
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.2, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -50,7 +50,11 @@ sections:
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
{% data reusables.release-notes.2023-12-backup-utils-exit-early-redis %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %} [Updated: 2024-06-17]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.3, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -26,7 +26,11 @@ sections:
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
{% data reusables.release-notes.2023-12-backup-utils-exit-early-redis %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
{% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %} [Updated: 2024-06-17]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.4, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -31,8 +31,6 @@ sections:
|
||||
{% data reusables.release-notes.2023-11-cluster-ha-failover-git-push-failure %}
|
||||
- |
|
||||
{% data reusables.release-notes.2023-12-backup-utils-exit-early-redis %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
`ghe-migrations` visualizer is not working due to a known regression. As a results, users will not be able to use `ghe-migrations` to view the status of migrations during an upgrade. Instead you can inspect the log files in `/var/log/dbmigration` to get the status/progress of migrations.
|
||||
- |
|
||||
@@ -45,3 +43,9 @@ sections:
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
If a hotpatch upgrade requires the `haproxy-frontend` service to be restarted, the restart will hang if there are existing long-lived connections, such as browser web sockets or Git operations. No new connections will be accepted for up to 5 minutes. Any existing unfinished connections at this time will be disconnected.
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.2, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -157,8 +157,6 @@ sections:
|
||||
{% data reusables.release-notes.2023-11-cluster-ha-failover-git-push-failure %}
|
||||
- |
|
||||
{% data reusables.release-notes.2023-12-backup-utils-exit-early-redis %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Due to a known regression, operators will not be able to use the `ghe-migrations` visualizer to view the status of migrations during an upgrade. Instead, the operator can inspect the log files in `/var/log/dbmigration` to see the status and progress of migrations.
|
||||
- |
|
||||
@@ -167,3 +165,9 @@ sections:
|
||||
_Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised._
|
||||
- |
|
||||
If a hotpatch upgrade requires the `haproxy-frontend` service to be restarted, the restart will hang if there are existing long-lived connections, such as browser web sockets or Git operations. No new connections will be accepted for up to 5 minutes. Any existing unfinished connections at this time will be disconnected.
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.7, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -91,8 +91,6 @@ sections:
|
||||
{% data reusables.release-notes.2023-11-cluster-ha-failover-git-push-failure %}
|
||||
- |
|
||||
{% data reusables.release-notes.2023-12-backup-utils-exit-early-redis %}
|
||||
- |
|
||||
Repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Due to a known regression, operators will not be able to use the `ghe-migrations` visualizer to view the status of migrations during an upgrade. Instead, the operator can inspect the log files in `/var/log/dbmigration` to see the status and progress of migrations.
|
||||
- |
|
||||
@@ -114,4 +112,8 @@ sections:
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.8 when log forwarding is enabled, some forwarded log entries may be duplicated.
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12.7](/admin/release-notes#3.12.7-bugs). [Updated: 2024-09-16]
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12.7](/admin/release-notes#3.12.7-bugs). [Updated: 2024-09-16]
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.8, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -54,8 +54,6 @@ sections:
|
||||
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`.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
@@ -66,3 +64,9 @@ sections:
|
||||
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
|
||||
- |
|
||||
Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run.
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.12.9, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -38,8 +38,6 @@ sections:
|
||||
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)."
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
For an instance in a cluster configuration and with GitHub Actions enabled, restoring a cluster from backup requires targeting the primary DB node.
|
||||
- |
|
||||
@@ -56,3 +54,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.13.10, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -48,8 +48,6 @@ sections:
|
||||
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)."
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
For an instance in a cluster configuration and with GitHub Actions enabled, restoring a cluster from backup requires targeting the primary DB node.
|
||||
- |
|
||||
@@ -69,3 +67,8 @@ sections:
|
||||
errata:
|
||||
- |
|
||||
The warning and known issues section have been updated to accurately reflect that instances installed on GCP will face issues while hotpatching to 3.13.11. Previously, the warning and known issue indicated that customers would face issues either while upgrading or hotpatching to version 3.13.11. [Updated: 2025-03-11]
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.13.11, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -58,8 +58,6 @@ sections:
|
||||
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).
|
||||
- |
|
||||
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`.
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
For an instance in a cluster configuration and with GitHub Actions enabled, restoring a cluster from backup requires targeting the primary DB node.
|
||||
- |
|
||||
@@ -86,4 +84,9 @@ sections:
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- 'The [Known issues](/admin/release-notes#3.13.4-known-issues) section previously indicated that `Instance setup in AWS with IMDSv2 enforced fails if no public IP is present` is still an issue. The issue is resolved and is documented in the [Bug fixes](/admin/release-notes#3.13.4-bugs) section. [Updated: 2024-09-30]'
|
||||
- |
|
||||
The [Known issues](/admin/release-notes#3.13.4-known-issues) section previously indicated that `Instance setup in AWS with IMDSv2 enforced fails if no public IP is present` is still an issue. The issue is resolved and is documented in the [Bug fixes](/admin/release-notes#3.13.4-bugs) section. [Updated: 2024-09-30]
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.13.4, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -42,8 +42,6 @@ sections:
|
||||
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).
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
Repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
For an instance in a cluster configuration and with GitHub Actions enabled, restoring a cluster from backup requires targeting the primary DB node.
|
||||
- |
|
||||
@@ -64,3 +62,10 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.13.5, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -46,8 +46,6 @@ sections:
|
||||
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. See [AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account).
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
Repositories originally imported using `ghe-migrator` will not correctly track GitHub Advanced Security contributions.
|
||||
- |
|
||||
For an instance in a cluster configuration and with GitHub Actions enabled, restoring a cluster from backup requires targeting the primary DB node.
|
||||
- |
|
||||
@@ -70,3 +68,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.13.6, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -10,8 +10,6 @@ sections:
|
||||
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).
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
For an instance in a cluster configuration and with GitHub Actions enabled, restoring a cluster from backup requires targeting the primary DB node.
|
||||
- |
|
||||
@@ -34,3 +32,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.13.6, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -15,8 +15,6 @@ sections:
|
||||
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).
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
For an instance in a cluster configuration and with GitHub Actions enabled, restoring a cluster from backup requires targeting the primary DB node.
|
||||
- |
|
||||
@@ -35,3 +33,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.13.8, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -44,8 +44,6 @@ sections:
|
||||
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).
|
||||
- |
|
||||
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.
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
For an instance in a cluster configuration and with GitHub Actions enabled, restoring a cluster from backup requires targeting the primary DB node.
|
||||
- |
|
||||
@@ -62,3 +60,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.13.9, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -183,8 +183,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
REST API endpoints for admin stats may time out on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -244,3 +242,7 @@ sections:
|
||||
The "Changes" section indicated that "Pushes that update over 5,000 branches no longer trigger webhooks or GitHub Actions workflows." The change instead affects GitHub Enterprise Server version 3.15. [Updated: 2024-10-30]
|
||||
- |
|
||||
These release notes previously did not include a note for the deprecation of team discussions.
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.14.0, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -50,8 +50,6 @@ sections:
|
||||
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`.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -84,3 +82,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.14.1, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -56,8 +56,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
The admin stats REST API endpoints may time out on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -90,3 +88,9 @@ sections:
|
||||
deprecations:
|
||||
- |
|
||||
The option to "copy Storage settings from Actions" in the Management Console ("GitHub Packages" > "Packages Storage Settings") has been removed. [Updated: 2024-11-20]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.14.2, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -54,8 +54,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using `ghe-migrator` will not correctly track GitHub Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -84,3 +82,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.14.3, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -12,8 +12,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -44,3 +42,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.14.4, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -17,8 +17,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -45,3 +43,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.14.5, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -54,8 +54,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -80,3 +78,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.14.6, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -40,8 +40,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -66,3 +64,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.14.7, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
@@ -58,8 +58,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -87,3 +85,7 @@ sections:
|
||||
errata:
|
||||
- |
|
||||
The warning and known issues section have been updated to accurately reflect that instances installed on GCP will face issues while hotpatching to 3.14.8. Previously, the warning and known issue indicated that customers would face issues either while upgrading or hotpatching to version 3.14.8. [Updated: 2025-03-11]
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.14.1, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -175,8 +175,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using `ghe-migrator` will not correctly track GitHub Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -228,3 +226,10 @@ sections:
|
||||
The Management Console API has been removed. The Manage GHES API reached feature parity with the Management Console API in {% data variables.product.prodname_ghe_server %} version 3.12. For information about the Manage GHES API, see [AUTOTITLE](/rest/enterprise-admin/manage-ghes).
|
||||
- |
|
||||
The option to "copy Storage settings from Actions" in the Management Console ("GitHub Packages" > "Packages Storage Settings") has been removed.
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.15.0, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -64,8 +64,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -101,3 +99,10 @@ sections:
|
||||
notes:
|
||||
- |
|
||||
Projects (classic) will be removed from GitHub Enterprise Server 3.16 and later. For more information, see [Sunset Notice – Projects (classic)](https://github.blog/changelog/2024-05-23-sunset-notice-projects-classic).
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.15.1, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -51,8 +51,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -81,3 +79,9 @@ sections:
|
||||
{% data reusables.release-notes.2025-03-03-elasticsearch-data-loss %}
|
||||
|
||||
[Updated: 2025-03-12]
|
||||
|
||||
errata:
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.15.2, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
@@ -62,8 +62,6 @@ sections:
|
||||
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.
|
||||
- |
|
||||
{% data reusables.release-notes.large-adoc-files-issue %}
|
||||
- |
|
||||
Repositories originally imported using ghe-migrator will not correctly track Advanced Security contributions.
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
@@ -95,3 +93,8 @@ sections:
|
||||
errata:
|
||||
- |
|
||||
The warning and known issues section have been updated to accurately reflect that instances installed on GCP will face issues while hotpatching to 3.15.3. Previously, the warning and known issue indicated that customers would face issues either while upgrading or hotpatching to version 3.15.3. [Updated: 2025-03-11]
|
||||
- |
|
||||
These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.15.3, repositories originally imported using `ghe-migrator` will not correctly track Advanced Security contributions.
|
||||
|
||||
The fix for this problem was already included in GitHub Enterprise Server [3.12](/admin/release-notes#3.12.0-bugs). [Updated: 2025-04-11]
|
||||
|
||||
Reference in New Issue
Block a user