Repo sync

content/copilot/reference/ai-models/model-hosting.md

@@ -83,6 +83,7 @@ Used for:
 
 * {% data variables.copilot.gemini_38_flash %}
 * {% data variables.copilot.gemini_4_argon %}
+* {% data variables.copilot.gemini_4_carbon %}
 
 {% data variables.product.prodname_copilot %} uses {% data variables.copilot.gemini %} models hosted on Google Cloud Platform (GCP). When using {% data variables.copilot.gemini %} models, prompts and metadata are sent to GCP, which makes the [following data commitment](https://cloud.google.com/vertex-ai/generative-ai/docs/data-governance): _{% data variables.copilot.gemini %} doesn't use your prompts, or its responses, as data to train its models._
 

content/copilot/reference/ai-models/supported-models.md

@@ -129,6 +129,7 @@ Some {% data variables.product.prodname_copilot_short %} models require minimum
 |----------------------------------------------------------|----------------------------------------------|------------------------------------------|----------------|-------|---------|
 | {% data variables.copilot.gemini_38_flash %}     | TBD | `17.14.22` or `18.1.0`         | TBD | TBD | TBD |
 | {% data variables.copilot.gemini_4_argon %}      | TBD | `17.14.22` or `18.1.0`         | TBD | TBD | TBD |
+| {% data variables.copilot.gemini_4_carbon %}     | TBD | TBD                            | TBD | TBD | TBD |
 | {% data variables.copilot.gpt_53_codex %}        | `v1.104.1` | `17.14.19`                     | `1.5.61` | `0.45.0` | `0.13.0` |
 | {% data variables.copilot.gpt_56_luna %}         | `1.128.0` | TBD | TBD | TBD | TBD |
 | {% data variables.copilot.gpt_56_sol %}          | `1.128.0` | TBD | TBD | TBD | TBD |

content/copilot/reference/copilot-billing/models-and-pricing.md

@@ -140,4 +140,6 @@ You can view your current {% data variables.product.prodname_actions %} usage fo
 
 [^gemini-4-argon-promo]: {% data variables.copilot.gemini_4_argon %} is available at the promotional pricing of $2.00 per 1M input tokens, $0.10 per 1M cached input tokens, and $10.00 per 1M output tokens until December 1, 2026.
 
+[^gemini-4-carbon-promo]: {% data variables.copilot.gemini_4_carbon %} is available at the promotional pricing of $2.00 per 1M input tokens, $0.10 per 1M cached input tokens, and $10.00 per 1M output tokens until December 1, 2026. Starting December 1, 2026, pricing is $4.00 per 1M input tokens, $0.20 per 1M cached input tokens, and $20.00 per 1M output tokens.
+
 <!-- end expires 2026-12-01 -->

data/release-notes/enterprise-server/3-19/15.yml

@@ -0,0 +1,46 @@
+date: '2026-11-10'
+sections:
+  security_fixes:
+    - |
+      **CRITICAL**: The Ruby Active Storage component was updated to address the file-read and remote code execution vulnerability CVE-2026-66066.
+    - |
+      **HIGH**: Updated Git to include fixes that address CVE-2026-105437, CVE-2026-111760, CVE-2026-113408, CVE-2026-114466, CVE-2026-114467, and CVE-2026-114469.
+    - |
+      **MODERATE**: The Brotli compression library bundled with the GitHub application was updated to address CVE-2026-111497.
+    - |
+      Security updates have been applied to Go, OpenSSL, and Ubuntu system packages, including SQLite, across targeted main and bundled container images. These updates partially address [CVE-2026-111943](https://www.cve.org/CVERecord?id=CVE-2026-111943), [CVE-2025-15467](https://www.cve.org/CVERecord?id=CVE-2025-15467), and [CVE-2025-6965](https://www.cve.org/CVERecord?id=CVE-2025-6965); remaining components will be updated in a future release.
+    - |
+      Packages have been updated to the latest security versions.
+  known_issues:
+    - |
+      During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading.
+    - |
+      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/administering-your-instance/administering-your-instance-from-the-web-ui/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account).
+    - |
+      {% data reusables.release-notes.large-adoc-files-issue %}
+    - |
+      Admin stats REST API endpoints may time out on appliances with many users or repositories. Retrying the request until data is returned is advised.
+    - |
+      When following the steps for [Replacing the primary database node](/admin/monitoring-and-managing-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-the-primary-database-node-mysql-or-mysql-and-mssql), running `ghe-cluster-config-apply` might fail with errors. If this occurs, re-running `ghe-cluster-config-apply` is expected to succeed.
+    - |
+      Running a config apply as part of the steps for [Replacing a node in an emergency](/admin/monitoring-and-managing-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-a-node-in-an-emergency) may fail with errors if the node being replaced is still reachable. If this occurs, shut down the node and repeat the steps.
+    - |
+      {% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %}
+    - |
+      When restoring data originally backed up from a 3.13 or greater appliance version, the Elasticsearch indices need to be reindexed before some of the data will show up. This happens via a scheduled job that runs on the first Saturday of each month. It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`.
+    - |
+      When enabling automatic update checks for the first time in the Management Console, the status is not dynamically reflected until the "Updates" page is reloaded.
+    - |
+      When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
+    - |
+      When initializing a new GHES cluster, nodes with the `consul-server` role should be added to the cluster before adding additional nodes. Adding all nodes simultaneously creates a race condition between nomad server registration and nomad client registration.
+    - |
+      In a cluster, the host running restore requires access to the storage nodes via their private IPs.
+    - |
+      After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance.
+    - |
+      After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows.
+    - |
+      The setting to define private registries at the organization level for code scanning is only available if Dependabot is also enabled for the instance.
+    - |
+      After a restart, an instance can remain unavailable with "Starting..." displayed in the web interface. To recover, an administrator can connect using administrative SSH and rerun `ghe-config-apply`. This provides temporary recovery but does not prevent the issue from recurring. This issue is resolved in {% data variables.product.prodname_ghe_server %} 3.21.0 and later.

data/release-notes/enterprise-server/3-20/11.yml

@@ -0,0 +1,45 @@
+date: '2026-11-10'
+sections:
+  security_fixes:
+    - |
+      **CRITICAL**: The Ruby Active Storage component was updated to address the file-read and remote code execution vulnerability CVE-2026-66066.
+    - |
+      **HIGH**: Updated Git to include fixes that address CVE-2026-105437, CVE-2026-111760, CVE-2026-113408, CVE-2026-114466, CVE-2026-114467, and CVE-2026-114469.
+    - |
+      **MODERATE**: The Brotli compression library bundled with the GitHub application was updated to address CVE-2026-111497.
+    - |
+      Security updates have been applied to Go, OpenSSL, and Ubuntu system packages, including SQLite, across targeted main and bundled container images. These updates partially address [CVE-2026-111943](https://www.cve.org/CVERecord?id=CVE-2026-111943), [CVE-2025-15467](https://www.cve.org/CVERecord?id=CVE-2025-15467), and [CVE-2025-6965](https://www.cve.org/CVERecord?id=CVE-2025-6965); remaining components will be updated in a future release. 
+    - |
+      Packages have been updated to the latest security versions.
+  bugs:
+    - |
+      On large instances with a license for {% data variables.product.prodname_GHAS %}, applying a security configuration to many repositories could time out while checking license usage, leaving repositories that failed to enable. License usage checks are now faster under concurrent load.
+  known_issues:
+    - |
+      During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading.
+    - |
+      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/administering-your-instance/administering-your-instance-from-the-web-ui/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account).
+    - |
+      {% data reusables.release-notes.large-adoc-files-issue %}
+    - |
+      Admin stats REST API endpoints may time out on appliances with many users or repositories. Retrying the request until data is returned is advised.
+    - |
+      When following the steps for [Replacing the primary database node](/admin/monitoring-and-managing-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-the-primary-database-node-mysql-or-mysql-and-mssql), running `ghe-cluster-config-apply` might fail with errors. If this occurs, re-running `ghe-cluster-config-apply` is expected to succeed.
+    - |
+      Running a config apply as part of the steps for [Replacing a node in an emergency](/admin/monitoring-and-managing-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-a-node-in-an-emergency) may fail with errors if the node being replaced is still reachable. If this occurs, shut down the node and repeat the steps.
+    - |
+      When restoring data originally backed up from a 3.13 or greater appliance version, the Elasticsearch indices need to be reindexed before some of the data will show up. This happens via a scheduled job that runs on the first Saturday of each month. It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`.
+    - |
+      When initializing a new GHES cluster, nodes with the `consul-server` role should be added to the cluster before adding additional nodes. Adding all nodes simultaneously creates a race condition between nomad server registration and nomad client registration.
+    - |
+      In a cluster, the host running restore requires access to the storage nodes via their private IPs.
+    - |
+      After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance.
+    - |
+      After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows.
+    - |
+      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 an administrator restores a backup with `ghe-restore` 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 ...`. If you see this warning or storage data is missing after a restore, contact GitHub Support.
+    - |
+      After a restart, an instance can remain unavailable with "Starting..." displayed in the web interface. To recover, an administrator can connect using administrative SSH and rerun `ghe-config-apply`. This provides temporary recovery but does not prevent the issue from recurring. This issue is resolved in {% data variables.product.prodname_ghe_server %} 3.21.0 and later.

data/release-notes/enterprise-server/3-21/9.yml

@@ -0,0 +1,47 @@
+date: '2026-11-10'
+sections:
+  security_fixes:
+    - |
+      **CRITICAL**: The Ruby Active Storage component was updated to address the file-read and remote code execution vulnerability CVE-2026-66066.
+    - |
+      **HIGH**: Updated Git to include fixes that address CVE-2026-105437, CVE-2026-111760, CVE-2026-113408, CVE-2026-114466, CVE-2026-114467, and CVE-2026-114469. 
+    - |
+      **MODERATE**: The Brotli compression library bundled with the GitHub application was updated to address CVE-2026-111497.
+    - |
+      Security updates have been applied to Go, OpenSSL, and Ubuntu system packages, including SQLite, across targeted main and bundled container images. These updates partially address [CVE-2026-111943](https://www.cve.org/CVERecord?id=CVE-2026-111943), [CVE-2025-15467](https://www.cve.org/CVERecord?id=CVE-2025-15467), and [CVE-2025-6965](https://www.cve.org/CVERecord?id=CVE-2025-6965); remaining components will be updated in a future release. 
+    - |
+      Packages have been updated to the latest security versions.
+  bugs:
+    - |
+      On large instances with a license for {% data variables.product.prodname_GHAS %}, applying a security configuration to many repositories could time out while checking license usage, leaving repositories that failed to enable. License usage checks are now faster under concurrent load.
+  known_issues:
+    - |
+      During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading.
+    - |
+      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/administering-your-instance/administering-your-instance-from-the-web-ui/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account).
+    - |
+      {% data reusables.release-notes.large-adoc-files-issue %}
+    - |
+      Admin stats REST API endpoints may time out on appliances with many users or repositories. Retrying the request until data is returned is advised.
+    - |
+      When following the steps for [Replacing the primary database node](/admin/monitoring-and-managing-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-the-primary-database-node-mysql-or-mysql-and-mssql), running `ghe-cluster-config-apply` might fail with errors. If this occurs, re-running `ghe-cluster-config-apply` is expected to succeed.
+    - |
+      Running a config apply as part of the steps for [Replacing a node in an emergency](/admin/monitoring-and-managing-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-a-node-in-an-emergency) may fail with errors if the node being replaced is still reachable. If this occurs, shut down the node and repeat the steps.
+    - |
+      When restoring data originally backed up from a 3.13 or greater appliance version, the Elasticsearch indices need to be reindexed before some of the data will show up. This happens via a scheduled job that runs on the first Saturday of each month. It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`.
+    - |
+      When initializing a new GHES cluster, nodes with the `consul-server` role should be added to the cluster before adding additional nodes. Adding all nodes simultaneously creates a race condition between nomad server registration and nomad client registration.
+    - |
+      In a cluster, the host running restore requires access to the storage nodes via their private IPs.
+    - |
+      After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance.
+    - |
+      After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows.
+    - |
+      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 an administrator restores a backup with `ghe-restore` 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 ...`. If you see this warning or storage data is missing after a restore, contact GitHub Support.
+    - |
+      In some cases, pull requests using auto-merge or merge queue may not merge automatically until mergeability is recalculated.
+    - |
+      On a newly booted GitHub Enterprise 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.