From 6cd81438c064a4e0d11d6844389600224eff2411 Mon Sep 17 00:00:00 2001 From: Ryan Trauntvein Date: Wed, 25 Mar 2026 16:01:19 -0700 Subject: [PATCH] Fix haproxy-nbthread config key in release notes The ghe-config key requires the core. prefix: ghe-config core.haproxy-nbthread (not ghe-config haproxy-nbthread) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- data/release-notes/enterprise-server/3-16/16.yml | 2 +- data/release-notes/enterprise-server/3-17/13.yml | 2 +- data/release-notes/enterprise-server/3-18/7.yml | 2 +- data/release-notes/enterprise-server/3-19/4.yml | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/data/release-notes/enterprise-server/3-16/16.yml b/data/release-notes/enterprise-server/3-16/16.yml index ea820b95730d..f80709891722 100644 --- a/data/release-notes/enterprise-server/3-16/16.yml +++ b/data/release-notes/enterprise-server/3-16/16.yml @@ -26,7 +26,7 @@ sections: Users experienced failures when migrating repositories with releases using GitHub Enterprise Importer. Migrations failed to import release assets that were incompletely uploaded at the time of export, as the export archive referenced assets without including the corresponding files. changes: - | - To improve performance on large instances, HAProxy automatically scales its thread count based on available CPUs and uses higher connection limits for high-traffic backend services including GitHub Actions, database connections, job queues, and package registry. Administrators can override the thread count using `ghe-config haproxy-nbthread` if needed. + To improve performance on large instances, HAProxy automatically scales its thread count based on available CPUs and uses higher connection limits for high-traffic backend services including GitHub Actions, database connections, job queues, and package registry. Administrators can override the thread count using `ghe-config core.haproxy-nbthread` if needed. - | On instances with a license for GitHub Advanced Security, code scanning-specific rate limits have been lifted and aligned with the default GitHub rate limits. Users can access higher limits through an exemption mechanism. known_issues: diff --git a/data/release-notes/enterprise-server/3-17/13.yml b/data/release-notes/enterprise-server/3-17/13.yml index 6dabd1366221..5fe967fabedc 100644 --- a/data/release-notes/enterprise-server/3-17/13.yml +++ b/data/release-notes/enterprise-server/3-17/13.yml @@ -28,7 +28,7 @@ sections: Users experienced failures when migrating repositories with releases using GitHub Enterprise Importer. Migrations failed to import release assets that were incompletely uploaded at the time of export, as the export archive referenced assets without including the corresponding files. changes: - | - To improve performance on large instances, HAProxy automatically scales its thread count based on available CPUs and uses higher connection limits for high-traffic backend services including GitHub Actions, database connections, job queues, and package registry. Administrators can override the thread count using `ghe-config haproxy-nbthread` if needed. + To improve performance on large instances, HAProxy automatically scales its thread count based on available CPUs and uses higher connection limits for high-traffic backend services including GitHub Actions, database connections, job queues, and package registry. Administrators can override the thread count using `ghe-config core.haproxy-nbthread` if needed. - | On instances with a license for GitHub Advanced Security, code scanning-specific rate limits have been lifted and aligned with the default GitHub rate limits. Users can access higher limits through an exemption mechanism. known_issues: diff --git a/data/release-notes/enterprise-server/3-18/7.yml b/data/release-notes/enterprise-server/3-18/7.yml index f1b171046855..808dfec4f01d 100644 --- a/data/release-notes/enterprise-server/3-18/7.yml +++ b/data/release-notes/enterprise-server/3-18/7.yml @@ -32,7 +32,7 @@ sections: Users experienced failures when migrating repositories with releases using GitHub Enterprise Importer. Migrations failed to import release assets that were incompletely uploaded at the time of export, as the export archive referenced assets without including the corresponding files. changes: - | - To improve performance on large instances, HAProxy automatically scales its thread count based on available CPUs and uses higher connection limits for high-traffic backend services including GitHub Actions, database connections, job queues, and package registry. Administrators can override the thread count using `ghe-config haproxy-nbthread` if needed. + To improve performance on large instances, HAProxy automatically scales its thread count based on available CPUs and uses higher connection limits for high-traffic backend services including GitHub Actions, database connections, job queues, and package registry. Administrators can override the thread count using `ghe-config core.haproxy-nbthread` if needed. - | API consumers can update issues via the REST API (PATCH) or the GraphQL `updateIssue` mutation using fine-grained permissions for closing and reopening issues, and for setting milestones. known_issues: diff --git a/data/release-notes/enterprise-server/3-19/4.yml b/data/release-notes/enterprise-server/3-19/4.yml index d78f3c32d326..7dec71eb7e6f 100644 --- a/data/release-notes/enterprise-server/3-19/4.yml +++ b/data/release-notes/enterprise-server/3-19/4.yml @@ -46,7 +46,7 @@ sections: After upgrading to 3.19, site administrators could not delete users via the Management Console or the REST API. User deletion attempts returned a `500 Internal Server Error`. changes: - | - To improve performance on large instances, HAProxy automatically scales its thread count based on available CPUs and uses higher connection limits for high-traffic backend services including GitHub Actions, database connections, job queues, and package registry. Administrators can override the thread count using `ghe-config haproxy-nbthread` if needed. + To improve performance on large instances, HAProxy automatically scales its thread count based on available CPUs and uses higher connection limits for high-traffic backend services including GitHub Actions, database connections, job queues, and package registry. Administrators can override the thread count using `ghe-config core.haproxy-nbthread` if needed. - | API consumers can update issues via the REST API (PATCH) using fine-grained permissions for closing and reopening issues, and for setting milestones. - |