From 803e5aa4c071a7268667fb1b7c0e588a021c45c6 Mon Sep 17 00:00:00 2001 From: Stephanie Sabota <80356791+steph-sabotasan@users.noreply.github.com> Date: Mon, 26 Oct 2026 16:35:12 +0000 Subject: [PATCH 1/3] Correct GHES Replication Controller storage restore known issue (#64362) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> --- data/release-notes/enterprise-server/3-20/6.yml | 2 +- data/release-notes/enterprise-server/3-20/7.yml | 2 +- data/release-notes/enterprise-server/3-20/8.yml | 2 +- data/release-notes/enterprise-server/3-20/9.yml | 2 +- data/release-notes/enterprise-server/3-21/4.yml | 2 +- data/release-notes/enterprise-server/3-21/5.yml | 2 +- data/release-notes/enterprise-server/3-21/6.yml | 2 +- data/release-notes/enterprise-server/3-21/7.yml | 2 +- data/release-notes/enterprise-server/3-22/0.yml | 2 +- data/release-notes/enterprise-server/3-22/1.yml | 5 +++-- data/release-notes/enterprise-server/3-22/2.yml | 4 ++-- 11 files changed, 14 insertions(+), 13 deletions(-) diff --git a/data/release-notes/enterprise-server/3-20/6.yml b/data/release-notes/enterprise-server/3-20/6.yml index dddbd0d56fe7..e25337a67680 100644 --- a/data/release-notes/enterprise-server/3-20/6.yml +++ b/data/release-notes/enterprise-server/3-20/6.yml @@ -97,4 +97,4 @@ sections: - | On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`. - | - When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored. [Updated: 2026-08-27] + When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Replication Controller is disabled by default in {% data variables.product.prodname_ghe_server %} 3.20. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22] diff --git a/data/release-notes/enterprise-server/3-20/7.yml b/data/release-notes/enterprise-server/3-20/7.yml index ccfc8547d88f..5062aa9455f0 100644 --- a/data/release-notes/enterprise-server/3-20/7.yml +++ b/data/release-notes/enterprise-server/3-20/7.yml @@ -90,4 +90,4 @@ sections: - | On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`. - | - When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored. + When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Replication Controller is disabled by default in {% data variables.product.prodname_ghe_server %} 3.20. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22] diff --git a/data/release-notes/enterprise-server/3-20/8.yml b/data/release-notes/enterprise-server/3-20/8.yml index 3f9ee4a51b9f..53061b29431d 100644 --- a/data/release-notes/enterprise-server/3-20/8.yml +++ b/data/release-notes/enterprise-server/3-20/8.yml @@ -110,4 +110,4 @@ sections: - | On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`. - | - _When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored._ + When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Replication Controller is disabled by default in {% data variables.product.prodname_ghe_server %} 3.20. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22] diff --git a/data/release-notes/enterprise-server/3-20/9.yml b/data/release-notes/enterprise-server/3-20/9.yml index b1419ffc2738..093a6d487c76 100644 --- a/data/release-notes/enterprise-server/3-20/9.yml +++ b/data/release-notes/enterprise-server/3-20/9.yml @@ -66,7 +66,7 @@ sections: - | On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`. - | - When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored. + When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Replication Controller is disabled by default in {% data variables.product.prodname_ghe_server %} 3.20. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22] errata: - | The known issues incorrectly indicated that Elasticsearch indices are reindexed by a nightly scheduled job after restoring data backed up from GitHub Enterprise Server 3.13 or later. The scheduled job runs on the first Saturday of each month. [Updated: 2026-10-15] diff --git a/data/release-notes/enterprise-server/3-21/4.yml b/data/release-notes/enterprise-server/3-21/4.yml index 218ef32ba54a..8a4e00aed479 100644 --- a/data/release-notes/enterprise-server/3-21/4.yml +++ b/data/release-notes/enterprise-server/3-21/4.yml @@ -96,4 +96,4 @@ sections: - | On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`. - | - When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored. [Updated: 2026-08-27] + When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, which is the default in {% data variables.product.prodname_ghe_server %} 3.21, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Restores with {% data variables.product.prodname_enterprise_backup_service %} on {% data variables.product.prodname_ghe_server %} 3.21.6 or later aren't affected. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22] diff --git a/data/release-notes/enterprise-server/3-21/5.yml b/data/release-notes/enterprise-server/3-21/5.yml index 100521015d2b..769219d4d26b 100644 --- a/data/release-notes/enterprise-server/3-21/5.yml +++ b/data/release-notes/enterprise-server/3-21/5.yml @@ -96,6 +96,6 @@ sections: - | After upgrading to GHES 3.21, scheduled Dependabot version updates may stop running for pre-existing configurations. If you have already upgraded and want to trigger scheduled version updates, save a change to each affected repository’s `.github/dependabot.yml` file. - | - When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored. + When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, which is the default in {% data variables.product.prodname_ghe_server %} 3.21, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Restores with {% data variables.product.prodname_enterprise_backup_service %} on {% data variables.product.prodname_ghe_server %} 3.21.6 or later aren't affected. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22] - | In clustered GitHub Enterprise Server environments, administrators may find that nodes that remain in the cluster but no longer have the `git-server`, `pages-server`, or `storage-server` role remain online and eligible to vote in the corresponding replication tables. Review role-specific replication state and contact GitHub Support if stale rows affect replication. diff --git a/data/release-notes/enterprise-server/3-21/6.yml b/data/release-notes/enterprise-server/3-21/6.yml index 83b786cdb55b..6df7abc44d71 100644 --- a/data/release-notes/enterprise-server/3-21/6.yml +++ b/data/release-notes/enterprise-server/3-21/6.yml @@ -124,6 +124,6 @@ sections: - | In clustered GitHub Enterprise Server environments, administrators may find that nodes that remain in the cluster but no longer have the `git-server`, `pages-server`, or `storage-server` role remain online and eligible to vote in the corresponding replication tables. Review role-specific replication state and contact GitHub Support if stale rows affect replication. - | - _When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored._ + When an administrator uses {% data variables.product.prodname_enterprise_backup_utilities %} to restore a backup to a configured standalone instance with Replication Controller enabled, which is the default in {% data variables.product.prodname_ghe_server %} 3.21, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Restores with {% data variables.product.prodname_enterprise_backup_service %} on {% data variables.product.prodname_ghe_server %} 3.21.6 or later aren't affected. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22] - | _On a newly booted {% data variables.product.prodname_ghe_server %} instance, the merge box on a newly created pull request can stay on "Checking for the ability to merge automatically" and not show the merge status. If encountered, refreshing the page shows the correct merge status._ diff --git a/data/release-notes/enterprise-server/3-21/7.yml b/data/release-notes/enterprise-server/3-21/7.yml index dacf5eea9f95..99aaf24f46a4 100644 --- a/data/release-notes/enterprise-server/3-21/7.yml +++ b/data/release-notes/enterprise-server/3-21/7.yml @@ -72,7 +72,7 @@ sections: - | In a clustered GitHub Enterprise Server environment, a node that remained in the cluster after losing the `git-server`, `pages-server`, or `storage-server` role could continue to appear online and eligible for replication. This could cause replica placement failures, incorrect replica counts, or replication status to show a node without the relevant service as healthy. If you experience these symptoms, contact GitHub Support. - | - When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored. + When an administrator uses {% data variables.product.prodname_enterprise_backup_utilities %} to restore a backup to a configured standalone instance with Replication Controller enabled, which is the default in {% data variables.product.prodname_ghe_server %} 3.21, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. Restores with {% data variables.product.prodname_enterprise_backup_service %} on {% data variables.product.prodname_ghe_server %} 3.21.6 or later aren't affected. If you see this warning or storage data is missing after a restore, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22] - | On a newly booted {% data variables.product.prodname_ghe_server %} instance, the merge box on a newly created pull request can stay on "Checking for the ability to merge automatically" and not show the merge status. If encountered, refreshing the page shows the correct merge status. errata: diff --git a/data/release-notes/enterprise-server/3-22/0.yml b/data/release-notes/enterprise-server/3-22/0.yml index f5ebdb07c557..d98ef264eddb 100644 --- a/data/release-notes/enterprise-server/3-22/0.yml +++ b/data/release-notes/enterprise-server/3-22/0.yml @@ -238,7 +238,7 @@ sections: - | After upgrading to {% data variables.product.prodname_ghe_server %} 3.22, scheduled {% data variables.product.prodname_dependabot_version_updates %} may stop running for pre-existing configurations. If you have already upgraded and want to trigger scheduled version updates, save a change to each affected repository's `.github/dependabot.yml` file. - | - When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored. + When an administrator restores a backup to a configured standalone instance with Replication Controller enabled, `ghe-restore` may skip storage data, such as avatars and attachments, and still complete successfully. The restore output includes `Warning: no routes found, skipping storage restore ...`. This issue is fixed in {% data variables.product.prodname_ghe_server %} 3.22.1. If you see this warning or storage data is missing after a restore on {% data variables.product.prodname_ghe_server %} 3.22.0, contact {% data variables.contact.github_support %}. [Updated: 2026-10-22] - | In clustered {% data variables.product.prodname_ghe_server %} environments, nodes that remain in the cluster after losing the `git-server`, `pages-server`, or `storage-server` role may stay online and remain eligible to vote in the corresponding replication tables. Review the replication state for each role, and contact {% data variables.contact.github_support %} if stale rows affect replication. - | diff --git a/data/release-notes/enterprise-server/3-22/1.yml b/data/release-notes/enterprise-server/3-22/1.yml index 87e5d3665365..a11e882a6454 100644 --- a/data/release-notes/enterprise-server/3-22/1.yml +++ b/data/release-notes/enterprise-server/3-22/1.yml @@ -119,7 +119,8 @@ sections: After upgrading to GHES 3.21, scheduled Dependabot version updates may stop running for pre-existing configurations. If you have already upgraded and want to trigger scheduled version updates, save a change to each affected repository’s `.github/dependabot.yml` file. - | In clustered GitHub Enterprise Server environments, administrators may find that nodes that remain in the cluster but no longer have the `git-server`, `pages-server`, or `storage-server` role remain online and eligible to vote in the corresponding replication tables. Review role-specific replication state and contact GitHub Support if stale rows affect replication. - - | - _When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored._ - | _On a newly booted {% data variables.product.prodname_ghe_server %} instance, the merge box on a newly created pull request can stay on "Checking for the ability to merge automatically" and not show the merge status. If encountered, refreshing the page shows the correct merge status._ + errata: + - | + The known issues incorrectly indicated that this release doesn't restore the storage directory when you restore an instance with `ghe-restore` while Replication Controller is enabled. This issue is fixed in this release. [Updated: 2026-10-22] diff --git a/data/release-notes/enterprise-server/3-22/2.yml b/data/release-notes/enterprise-server/3-22/2.yml index fce3e9cf824b..de519855b999 100644 --- a/data/release-notes/enterprise-server/3-22/2.yml +++ b/data/release-notes/enterprise-server/3-22/2.yml @@ -68,10 +68,10 @@ sections: After upgrading to GHES 3.21, scheduled Dependabot version updates may stop running for pre-existing configurations. If you have already upgraded and want to trigger scheduled version updates, save a change to each affected repository’s `.github/dependabot.yml` file. - | In a clustered GitHub Enterprise Server environment, a node that remained in the cluster after losing the `git-server`, `pages-server`, or `storage-server` role could continue to appear online and eligible for replication. This could cause replica placement failures, incorrect replica counts, or replication status to show a node without the relevant service as healthy. If you experience these symptoms, contact GitHub Support. - - | - When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored. - | On a newly booted {% data variables.product.prodname_ghe_server %} instance, the merge box on a newly created pull request can stay on "Checking for the ability to merge automatically" and not show the merge status. If encountered, refreshing the page shows the correct merge status. errata: - | The known issues incorrectly indicated that Elasticsearch indices are reindexed by a nightly scheduled job after restoring data backed up from GitHub Enterprise Server 3.13 or later. The scheduled job runs on the first Saturday of each month. [Updated: 2026-10-15] + - | + The known issues incorrectly indicated that this release doesn't restore the storage directory when you restore an instance with `ghe-restore` while Replication Controller is enabled. This issue was fixed in {% data variables.product.prodname_ghe_server %} 3.22.1. [Updated: 2026-10-22] From 3faa1fcdbf882979e5372564c2468d5032d19ed6 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 26 Oct 2026 16:39:31 +0000 Subject: [PATCH 2/3] Bump the npm_and_yarn group across 1 directory with 2 updates (#64389) Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- package-lock.json | 106 +++++++++++++++++++++++----------------------- package.json | 2 +- 2 files changed, 54 insertions(+), 54 deletions(-) diff --git a/package-lock.json b/package-lock.json index 06cf31381d95..0a27f9cc509c 100644 --- a/package-lock.json +++ b/package-lock.json @@ -63,7 +63,7 @@ "mdast-util-to-hast": "^13.2.1", "mdast-util-to-markdown": "2.1.2", "mdast-util-to-string": "^4.0.0", - "next": "^16.3.8", + "next": "^16.4.1", "parse5": "8.0.1", "pele": "1.3.0", "quick-lru": "7.0.1", @@ -2181,15 +2181,15 @@ } }, "node_modules/@next/env": { - "version": "16.3.8", - "resolved": "https://registry.npmjs.org/@next/env/-/env-16.3.8.tgz", - "integrity": "sha512-Al9zqHVV7TJv0eFuOU4U7Lvv74PTih4Ch63sk2xCIpSTkE3udFnaOcnzP2lQVymiL7yS9Cj2iClUXlR3EQ5sEw==", + "version": "16.4.1", + "resolved": "https://registry.npmjs.org/@next/env/-/env-16.4.1.tgz", + "integrity": "sha512-5sUUrrSvs/2/2LnLoesybMGx12EtPB46fdZ6RhAw0XDGSPxU2LFyQBB7yuEiOFFJPKmBY6+q2jTr1/AMbnp0/g==", "license": "MIT" }, "node_modules/@next/swc-darwin-arm64": { - "version": "16.3.8", - "resolved": "https://registry.npmjs.org/@next/swc-darwin-arm64/-/swc-darwin-arm64-16.3.8.tgz", - "integrity": "sha512-2JPRMh2nmQG5CiL7cXGL9AGwnPWJQ//cTtAUCT+w511QHk79SYz3LGv/pc5X643B/WEO0rvu3Yww0hqwt3kgeA==", + "version": "16.4.1", + "resolved": "https://registry.npmjs.org/@next/swc-darwin-arm64/-/swc-darwin-arm64-16.4.1.tgz", + "integrity": "sha512-U+hQ5Gj3fpzf4fveTIF3dpUFYhaSW8vHhdAnbiIomzXzg7boreYFgBqprepXFtW4sw+aTttiNmg0gew/iFNhbg==", "cpu": [ "arm64" ], @@ -2203,9 +2203,9 @@ } }, "node_modules/@next/swc-darwin-x64": { - "version": "16.3.8", - "resolved": "https://registry.npmjs.org/@next/swc-darwin-x64/-/swc-darwin-x64-16.3.8.tgz", - "integrity": "sha512-GZtCCOBKJ4leVIT/Th0llWKhD1ca92lzbQiS5R5ON9QkoiFnilFsebDae1JU2a3HWoKMEmEZWGs1AGLavVM72Q==", + "version": "16.4.1", + "resolved": "https://registry.npmjs.org/@next/swc-darwin-x64/-/swc-darwin-x64-16.4.1.tgz", + "integrity": "sha512-/hqC3V1XLUjhMASf/WridKdO9FXoEgN3HBWmtKbj00MPgnltutfraWJ3bYTpCRIgEIpbjJyOVLpYgAhh/BkdcQ==", "cpu": [ "x64" ], @@ -2219,9 +2219,9 @@ } }, "node_modules/@next/swc-linux-arm64-gnu": { - "version": "16.3.8", - "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-gnu/-/swc-linux-arm64-gnu-16.3.8.tgz", - "integrity": "sha512-O659ygeQYqneJ1fBKMpFxIFqYkYswu8IAS1OCKK/4f3ZgJJm1dRz4fVJZRi/kLLWjnBKnebOePA4WNv+sV1pVA==", + "version": "16.4.1", + "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-gnu/-/swc-linux-arm64-gnu-16.4.1.tgz", + "integrity": "sha512-GHzncHbcaS9g95kcvTNtKQW3aCLoR+xc3Jm7qrkpk1R+D2BjMHIPyvQGRPKCdMX95BsH/421jBUK06q9tEwzjw==", "cpu": [ "arm64" ], @@ -2238,9 +2238,9 @@ } }, "node_modules/@next/swc-linux-arm64-musl": { - "version": "16.3.8", - "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-musl/-/swc-linux-arm64-musl-16.3.8.tgz", - "integrity": "sha512-dSjKSyWpzxoO1d3DIZZcP4XJcNaKeLmxQMFOiYl5vuBRMmweIqnAhty8tAmRsvTss779cK1FtYnDMj40e4TQlg==", + "version": "16.4.1", + "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-musl/-/swc-linux-arm64-musl-16.4.1.tgz", + "integrity": "sha512-1SuJyDxW/PR9dHJat/ZRgcYLhuSZ+1psP4DlKb2tKIuXbjygqpLrJWRSq+onZQBv8LcmU67EIrmb6c3XTaJLjw==", "cpu": [ "arm64" ], @@ -2257,9 +2257,9 @@ } }, "node_modules/@next/swc-linux-x64-gnu": { - "version": "16.3.8", - "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-16.3.8.tgz", - "integrity": "sha512-lbqOuz3RPRcv+o9msNsJw5x4+Y1ZwPTs6vmL6DCf7i0fZfvng/F59wyeDwqHIvV0mK//RBy/jJkZ+nCKsSMXjQ==", + "version": "16.4.1", + "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-16.4.1.tgz", + "integrity": "sha512-Istng1hMGp9TGO4lUqeKLd70MPN/OOkucVTP2Nmj+gLkwBgmPqUw8CJYBCC7nbl/B/23bBCcjCI5Hsh6hazC1A==", "cpu": [ "x64" ], @@ -2276,9 +2276,9 @@ } }, "node_modules/@next/swc-linux-x64-musl": { - "version": "16.3.8", - "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-16.3.8.tgz", - "integrity": "sha512-+316WswI8ScVgZeUd+1KGaXkHhaYQzCjvH/05TZSpJ8zBizb1a4G7DtO7F12jcBIqMOtsz9ji1t48fmKtzqsGA==", + "version": "16.4.1", + "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-16.4.1.tgz", + "integrity": "sha512-aSC9wMNiZRRFVpPkPWBzRwLQxIGm/CiQcXyFF1XNcgodb+uMxdk7aSSGGpDXCbnvZdf4itjHxpOd5h7i7zaiYw==", "cpu": [ "x64" ], @@ -2295,9 +2295,9 @@ } }, "node_modules/@next/swc-win32-arm64-msvc": { - "version": "16.3.8", - "resolved": "https://registry.npmjs.org/@next/swc-win32-arm64-msvc/-/swc-win32-arm64-msvc-16.3.8.tgz", - "integrity": "sha512-ji0gd4kMYUxO+1fJBIbiBVRCjzG/lloiyCccnlebvb1ZJ5qXCPZqYg4Jl1DrrixnWNMKylzgpmMWx0yNDYXlzw==", + "version": "16.4.1", + "resolved": "https://registry.npmjs.org/@next/swc-win32-arm64-msvc/-/swc-win32-arm64-msvc-16.4.1.tgz", + "integrity": "sha512-t/myvwFDlypMUjRvbBf8qLPyuaB0iXYYdBtwMt6DM6f+60wtGr4bSYholdPqNeV5VUXZhrpMwfza829kmhS3iA==", "cpu": [ "arm64" ], @@ -2311,9 +2311,9 @@ } }, "node_modules/@next/swc-win32-x64-msvc": { - "version": "16.3.8", - "resolved": "https://registry.npmjs.org/@next/swc-win32-x64-msvc/-/swc-win32-x64-msvc-16.3.8.tgz", - "integrity": "sha512-WcTlaKt/TWkh5kUjdJcUmB1XgZ+1c6fz4Y9fDHL73YNSdGaUWjceeWrrlwF0nv19iABYWC4iAq1oX1w4Bn0vfg==", + "version": "16.4.1", + "resolved": "https://registry.npmjs.org/@next/swc-win32-x64-msvc/-/swc-win32-x64-msvc-16.4.1.tgz", + "integrity": "sha512-6ICqPo9awCkrtYNPhwkx1uU7rlFWrZRrIboDHS2LU+jv088UBYQtmJ25h6pCp27/+FZjF6BQ4Te4ErugyMeuBg==", "cpu": [ "x64" ], @@ -5855,18 +5855,18 @@ "license": "MIT" }, "node_modules/body-parser": { - "version": "2.3.0", - "resolved": "https://registry.npmjs.org/body-parser/-/body-parser-2.3.0.tgz", - "integrity": "sha512-2cGmJupaNgg+QUwVLAucDuWuoMZ6EX9iHDRswZ5lsNYEmwPaRknMPCLZz07yTzVq/83p4o/wzbDZbBrTvGGTIw==", + "version": "2.4.0", + "resolved": "https://registry.npmjs.org/body-parser/-/body-parser-2.4.0.tgz", + "integrity": "sha512-Ifk1KcLrxaGt1occQagQNFNNOqRt1LFuehEnHHzB8Z6cRgIxRU1TBaiIsUiCdA+gy5PL7Y1IX31DNKkRmxtXjQ==", "license": "MIT", "dependencies": { "bytes": "^3.1.2", - "content-type": "^2.0.0", + "content-type": "^2.1.0", "debug": "^4.4.3", "http-errors": "^2.0.1", - "iconv-lite": "^0.7.2", + "iconv-lite": "^0.7.3", "on-finished": "^2.4.1", - "qs": "^6.15.2", + "qs": "^6.16.1", "raw-body": "^3.0.2", "type-is": "^2.1.0" }, @@ -5879,9 +5879,9 @@ } }, "node_modules/body-parser/node_modules/content-type": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/content-type/-/content-type-2.0.0.tgz", - "integrity": "sha512-j/O/d7GcZCyNl7/hwZAb606rzqkyvaDctLmckbxLzHvFBzTJHuGEdodATcP3yIRoDrLHkIATJuvzbFlp/ki2cQ==", + "version": "2.1.0", + "resolved": "https://registry.npmjs.org/content-type/-/content-type-2.1.0.tgz", + "integrity": "sha512-mj7UPXE0jaqaOsukNZRUEfEi2AcL7C/vwmwcHV0O97eO1E1pxBZuyjlZrx5seTaNBg1U6+o35wpa35Qfcc+7ag==", "license": "MIT", "engines": { "node": ">=18" @@ -12076,12 +12076,12 @@ } }, "node_modules/next": { - "version": "16.3.8", - "resolved": "https://registry.npmjs.org/next/-/next-16.3.8.tgz", - "integrity": "sha512-U7QEZaTini6wKrb8A8hqLLqYQyCetegKjCpJOyxk642vWoMoU1x5PyZCJFvgYgiptA8xc5j/9xYlZFO7w9Sjmw==", + "version": "16.4.1", + "resolved": "https://registry.npmjs.org/next/-/next-16.4.1.tgz", + "integrity": "sha512-uc657V62E34fOI6W5NtG9IzwsPcms0Z60grz2MJGtglgD+pTFnNt4Yw2PzaU622tfX4vhrDgLZzicE2YlhI20Q==", "license": "MIT", "dependencies": { - "@next/env": "16.3.8", + "@next/env": "16.4.1", "@swc/helpers": "0.5.23", "baseline-browser-mapping": "^2.9.19", "caniuse-lite": "^1.0.30001579", @@ -12095,15 +12095,15 @@ "node": ">=20.9.0" }, "optionalDependencies": { - "@next/swc-darwin-arm64": "16.3.8", - "@next/swc-darwin-x64": "16.3.8", - "@next/swc-linux-arm64-gnu": "16.3.8", - "@next/swc-linux-arm64-musl": "16.3.8", - "@next/swc-linux-x64-gnu": "16.3.8", - "@next/swc-linux-x64-musl": "16.3.8", - "@next/swc-win32-arm64-msvc": "16.3.8", - "@next/swc-win32-x64-msvc": "16.3.8", - "sharp": "^0.35.4" + "@next/swc-darwin-arm64": "16.4.1", + "@next/swc-darwin-x64": "16.4.1", + "@next/swc-linux-arm64-gnu": "16.4.1", + "@next/swc-linux-arm64-musl": "16.4.1", + "@next/swc-linux-x64-gnu": "16.4.1", + "@next/swc-linux-x64-musl": "16.4.1", + "@next/swc-win32-arm64-msvc": "16.4.1", + "@next/swc-win32-x64-msvc": "16.4.1", + "sharp": "^0.35.5" }, "peerDependencies": { "@opentelemetry/api": "^1.1.0", @@ -12953,9 +12953,9 @@ } }, "node_modules/qs": { - "version": "6.16.0", - "resolved": "https://registry.npmjs.org/qs/-/qs-6.16.0.tgz", - "integrity": "sha512-h6fhOIaRrID2CbEY2fqs+7t+UXZo+MLAnU5gRIq85uFtdiUPCdsApMlHhXogKVM4HM2DVbIjGNTTYH2OcmP1vA==", + "version": "6.16.1", + "resolved": "https://registry.npmjs.org/qs/-/qs-6.16.1.tgz", + "integrity": "sha512-5Px6J7rfHBAGUhNQ3es4YzcOdBBw0SDcVtThJml4RdnKw4tKs2epA0kPZ+K8X+WiHktT93RHVcQ/3ym5aTCgtg==", "license": "BSD-3-Clause", "dependencies": { "es-define-property": "^1.0.1", diff --git a/package.json b/package.json index 231e81f4fc29..0b52884d7bda 100644 --- a/package.json +++ b/package.json @@ -222,7 +222,7 @@ "mdast-util-to-hast": "^13.2.1", "mdast-util-to-markdown": "2.1.2", "mdast-util-to-string": "^4.0.0", - "next": "^16.3.8", + "next": "^16.4.1", "parse5": "8.0.1", "pele": "1.3.0", "quick-lru": "7.0.1", From 6a353197c599fd234988764499b15c684a676628 Mon Sep 17 00:00:00 2001 From: docs-bot <77750099+docs-bot@users.noreply.github.com> Date: Mon, 26 Oct 2026 16:44:16 +0000 Subject: [PATCH 3/3] GraphQL schema update (#64409) Co-authored-by: github-merge-queue <118344674+github-merge-queue@users.noreply.github.com> --- src/graphql/data/fpt/changelog.json | 16 +++++++++++++ src/graphql/data/fpt/schema-repos.json | 28 +++++++++++++++++++++++ src/graphql/data/fpt/schema.docs.graphql | 20 ++++++++++++++++ src/graphql/data/ghec/schema-repos.json | 28 +++++++++++++++++++++++ src/graphql/data/ghec/schema.docs.graphql | 20 ++++++++++++++++ 5 files changed, 112 insertions(+) diff --git a/src/graphql/data/fpt/changelog.json b/src/graphql/data/fpt/changelog.json index 60c8057bd437..ea4e9f5c29ce 100644 --- a/src/graphql/data/fpt/changelog.json +++ b/src/graphql/data/fpt/changelog.json @@ -1,4 +1,20 @@ [ + { + "schemaChanges": [ + { + "title": "The GraphQL schema includes these changes:", + "changes": [ + "

Field ignoredFilePaths was added to object type FilePathRestrictionParameters

", + "

Input field ignoredFilePaths of type [String!] was added to input object type FilePathRestrictionParametersInput

", + "

Field ignoredFilePaths was added to object type MaxFileSizeParameters

", + "

Input field ignoredFilePaths of type [String!] was added to input object type MaxFileSizeParametersInput

" + ] + } + ], + "previewChanges": [], + "upcomingChanges": [], + "date": "2026-10-26" + }, { "schemaChanges": [ { diff --git a/src/graphql/data/fpt/schema-repos.json b/src/graphql/data/fpt/schema-repos.json index 39973b625ce2..5daf0ac8561d 100644 --- a/src/graphql/data/fpt/schema-repos.json +++ b/src/graphql/data/fpt/schema-repos.json @@ -760,6 +760,13 @@ "description": "

Prevent commits that include changes in specified file and folder paths from\nbeing pushed to the commit graph. This includes absolute paths that contain file names.

", "isDeprecated": false, "fields": [ + { + "name": "ignoredFilePaths", + "description": "

Files matching these patterns are allowed even when they also match a restricted path.

", + "type": "[String!]", + "id": "string", + "href": "/graphql/reference/other#scalar-string" + }, { "name": "restrictedFilePaths", "description": "

The file paths that are restricted from being pushed to the commit graph.

", @@ -930,6 +937,13 @@ "description": "

Prevent commits with individual files that exceed the specified limit from being pushed to the commit graph.

", "isDeprecated": false, "fields": [ + { + "name": "ignoredFilePaths", + "description": "

Files matching these patterns may exceed the maximum size.

", + "type": "[String!]", + "id": "string", + "href": "/graphql/reference/other#scalar-string" + }, { "name": "maxFileSize", "description": "

The maximum file size allowed in megabytes. This limit does not apply to Git Large File Storage (Git LFS).

", @@ -10454,6 +10468,13 @@ "description": "

Prevent commits that include changes in specified file and folder paths from\nbeing pushed to the commit graph. This includes absolute paths that contain file names.

", "isDeprecated": false, "inputFields": [ + { + "name": "ignoredFilePaths", + "description": "

Files matching these patterns are allowed even when they also match a restricted path.

", + "type": "[String!]", + "id": "string", + "href": "/graphql/reference/other#scalar-string" + }, { "name": "restrictedFilePaths", "description": "

The file paths that are restricted from being pushed to the commit graph.

", @@ -10512,6 +10533,13 @@ "description": "

Prevent commits with individual files that exceed the specified limit from being pushed to the commit graph.

", "isDeprecated": false, "inputFields": [ + { + "name": "ignoredFilePaths", + "description": "

Files matching these patterns may exceed the maximum size.

", + "type": "[String!]", + "id": "string", + "href": "/graphql/reference/other#scalar-string" + }, { "name": "maxFileSize", "description": "

The maximum file size allowed in megabytes. This limit does not apply to Git Large File Storage (Git LFS).

", diff --git a/src/graphql/data/fpt/schema.docs.graphql b/src/graphql/data/fpt/schema.docs.graphql index 8b827172b1ed..3ee9e0abadd7 100644 --- a/src/graphql/data/fpt/schema.docs.graphql +++ b/src/graphql/data/fpt/schema.docs.graphql @@ -18518,6 +18518,11 @@ Prevent commits that include changes in specified file and folder paths from being pushed to the commit graph. This includes absolute paths that contain file names. """ type FilePathRestrictionParameters @docsCategory(name: "repos") { + """ + Files matching these patterns are allowed even when they also match a restricted path. + """ + ignoredFilePaths: [String!] + """ The file paths that are restricted from being pushed to the commit graph. """ @@ -18529,6 +18534,11 @@ Prevent commits that include changes in specified file and folder paths from being pushed to the commit graph. This includes absolute paths that contain file names. """ input FilePathRestrictionParametersInput @docsCategory(name: "repos") { + """ + Files matching these patterns are allowed even when they also match a restricted path. + """ + ignoredFilePaths: [String!] + """ The file paths that are restricted from being pushed to the commit graph. """ @@ -25382,6 +25392,11 @@ input MaxFilePathLengthParametersInput @docsCategory(name: "repos") { Prevent commits with individual files that exceed the specified limit from being pushed to the commit graph. """ type MaxFileSizeParameters @docsCategory(name: "repos") { + """ + Files matching these patterns may exceed the maximum size. + """ + ignoredFilePaths: [String!] + """ The maximum file size allowed in megabytes. This limit does not apply to Git Large File Storage (Git LFS). """ @@ -25392,6 +25407,11 @@ type MaxFileSizeParameters @docsCategory(name: "repos") { Prevent commits with individual files that exceed the specified limit from being pushed to the commit graph. """ input MaxFileSizeParametersInput @docsCategory(name: "repos") { + """ + Files matching these patterns may exceed the maximum size. + """ + ignoredFilePaths: [String!] + """ The maximum file size allowed in megabytes. This limit does not apply to Git Large File Storage (Git LFS). """ diff --git a/src/graphql/data/ghec/schema-repos.json b/src/graphql/data/ghec/schema-repos.json index d26ab3453bd1..5eaf8c0acc67 100644 --- a/src/graphql/data/ghec/schema-repos.json +++ b/src/graphql/data/ghec/schema-repos.json @@ -760,6 +760,13 @@ "description": "

Prevent commits that include changes in specified file and folder paths from\nbeing pushed to the commit graph. This includes absolute paths that contain file names.

", "isDeprecated": false, "fields": [ + { + "name": "ignoredFilePaths", + "description": "

Files matching these patterns are allowed even when they also match a restricted path.

", + "type": "[String!]", + "id": "string", + "href": "/graphql/reference/other#scalar-string" + }, { "name": "restrictedFilePaths", "description": "

The file paths that are restricted from being pushed to the commit graph.

", @@ -930,6 +937,13 @@ "description": "

Prevent commits with individual files that exceed the specified limit from being pushed to the commit graph.

", "isDeprecated": false, "fields": [ + { + "name": "ignoredFilePaths", + "description": "

Files matching these patterns may exceed the maximum size.

", + "type": "[String!]", + "id": "string", + "href": "/graphql/reference/other#scalar-string" + }, { "name": "maxFileSize", "description": "

The maximum file size allowed in megabytes. This limit does not apply to Git Large File Storage (Git LFS).

", @@ -10454,6 +10468,13 @@ "description": "

Prevent commits that include changes in specified file and folder paths from\nbeing pushed to the commit graph. This includes absolute paths that contain file names.

", "isDeprecated": false, "inputFields": [ + { + "name": "ignoredFilePaths", + "description": "

Files matching these patterns are allowed even when they also match a restricted path.

", + "type": "[String!]", + "id": "string", + "href": "/graphql/reference/other#scalar-string" + }, { "name": "restrictedFilePaths", "description": "

The file paths that are restricted from being pushed to the commit graph.

", @@ -10512,6 +10533,13 @@ "description": "

Prevent commits with individual files that exceed the specified limit from being pushed to the commit graph.

", "isDeprecated": false, "inputFields": [ + { + "name": "ignoredFilePaths", + "description": "

Files matching these patterns may exceed the maximum size.

", + "type": "[String!]", + "id": "string", + "href": "/graphql/reference/other#scalar-string" + }, { "name": "maxFileSize", "description": "

The maximum file size allowed in megabytes. This limit does not apply to Git Large File Storage (Git LFS).

", diff --git a/src/graphql/data/ghec/schema.docs.graphql b/src/graphql/data/ghec/schema.docs.graphql index 8b827172b1ed..3ee9e0abadd7 100644 --- a/src/graphql/data/ghec/schema.docs.graphql +++ b/src/graphql/data/ghec/schema.docs.graphql @@ -18518,6 +18518,11 @@ Prevent commits that include changes in specified file and folder paths from being pushed to the commit graph. This includes absolute paths that contain file names. """ type FilePathRestrictionParameters @docsCategory(name: "repos") { + """ + Files matching these patterns are allowed even when they also match a restricted path. + """ + ignoredFilePaths: [String!] + """ The file paths that are restricted from being pushed to the commit graph. """ @@ -18529,6 +18534,11 @@ Prevent commits that include changes in specified file and folder paths from being pushed to the commit graph. This includes absolute paths that contain file names. """ input FilePathRestrictionParametersInput @docsCategory(name: "repos") { + """ + Files matching these patterns are allowed even when they also match a restricted path. + """ + ignoredFilePaths: [String!] + """ The file paths that are restricted from being pushed to the commit graph. """ @@ -25382,6 +25392,11 @@ input MaxFilePathLengthParametersInput @docsCategory(name: "repos") { Prevent commits with individual files that exceed the specified limit from being pushed to the commit graph. """ type MaxFileSizeParameters @docsCategory(name: "repos") { + """ + Files matching these patterns may exceed the maximum size. + """ + ignoredFilePaths: [String!] + """ The maximum file size allowed in megabytes. This limit does not apply to Git Large File Storage (Git LFS). """ @@ -25392,6 +25407,11 @@ type MaxFileSizeParameters @docsCategory(name: "repos") { Prevent commits with individual files that exceed the specified limit from being pushed to the commit graph. """ input MaxFileSizeParametersInput @docsCategory(name: "repos") { + """ + Files matching these patterns may exceed the maximum size. + """ + ignoredFilePaths: [String!] + """ The maximum file size allowed in megabytes. This limit does not apply to Git Large File Storage (Git LFS). """