From bc2b152dd56cc7a56a4a38aa3fb5364f87e1be1d Mon Sep 17 00:00:00 2001
From: Rob Aiken <rob@aiken.im>
Date: Fri, 11 Apr 2025 17:18:30 +0100
Subject: [PATCH 1/4] Add Dependabot ecosystem support for helm - [GA] [GA]
 #17730 (#55235)

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com>
---
 ...ss-to-private-registries-for-dependabot.md | 25 +++++++++++
 .../dependabot-options-reference.md           |  3 ++
 ...on-of-private-registries-for-dependabot.md | 43 ++++++++++++++++++-
 data/features/dependabot-helm-support.yml     |  6 +++
 .../dependabot/supported-package-managers.md  |  9 ++++
 5 files changed, 85 insertions(+), 1 deletion(-)
 create mode 100644 data/features/dependabot-helm-support.yml

diff --git a/content/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot.md b/content/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot.md
index ebcade2ee12f..50b859dd834c 100644
--- a/content/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot.md
+++ b/content/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot.md
@@ -256,6 +256,31 @@ registries:
 
 {% endraw %}
 
+{% ifversion dependabot-helm-support %}
+
+### `helm-registry`
+
+{% data variables.product.prodname_dependabot %} works with any OCI-compliant registries that implement the Open Container Initiative (OCI) Distribution Specification. For more information, see [Open Container Initiative Distribution Specification](https://github.com/opencontainers/distribution-spec/blob/main/spec.md) in the `opencontainers/distribution-spec` repository. {% data variables.product.prodname_dependabot %} supports authentication to private registries via a central token service or HTTP Basic Auth. For further details, see [Token Authentication Specification](https://helm.sh/docs/helm/helm_registry_login/) in the Docker documentation and [Basic access authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) on Wikipedia.
+
+The `helm-registry` type supports username and password. {% data reusables.dependabot.password-definition %}
+
+{% data reusables.dependabot.dependabot-updates-path-match %}
+
+{% raw %}
+
+```yaml copy
+registries:
+  helm_registry:
+    type: helm-registry
+    url: https://registry.example.com
+    username: octocat
+    password: ${{secrets.MY_REGISTRY_PASSWORD}}
+```
+
+{% endraw %}
+
+{% endif %}
+
 ### `hex-organization`
 
 The `hex-organization` type supports organization and key.
diff --git a/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md b/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md
index 244ef80ba9fa..e17815e3dabf 100644
--- a/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md
+++ b/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md
@@ -382,6 +382,9 @@ Package manager | YAML value      | Supported versions |
 | {% ifversion dependabot-dotnet-sdk %} |
 | .NET SDK       | `dotnet-sdk`         | >=.NET Core 3.1           |
 | {% endif %} |
+| {% ifversion dependabot-helm-support %} |
+| Helm Charts            | `helm`            | v3               |
+| {% endif %} |
 | Hex            | `mix`            | v1               |
 | elm-package    | `elm`            | v0.19            |
 | git submodule  | `gitsubmodule`   | Not applicable |
diff --git a/content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md b/content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md
index 46625fabd15b..00bcfd60e046 100644
--- a/content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md
+++ b/content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md
@@ -34,7 +34,8 @@ You'll find detailed guidance for the setup of the following package managers:
 * [Cargo](#cargo){% endif %}
 * [Docker](#docker){% ifversion dependabot-docker-compose-support %}
 * [Docker Compose](#docker-compose){% endif %}
-* [Gradle](#gradle)
+* [Gradle](#gradle){% ifversion dependabot-helm-support %}
+* [Helm Charts](#helm-charts){% endif %}
 * [Maven](#maven)
 * [npm](#npm)
 * [NuGet](#nuget){% ifversion dependabot-updates-pub-private-registry %}
@@ -169,6 +170,46 @@ Docker Compose adheres to the same configuration guidelines as Docker. For more
 
 {% endif %}
 
+{% ifversion dependabot-helm-support %}
+
+### Helm Charts
+
+Helm supports using a username and password for registries. For more information, see [AUTOTITLE](/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot#helm-registry).
+
+Snippet of `dependabot.yml` file using a username and password.
+
+{% raw %}
+
+```yaml copy
+registries:
+  helm_registry:
+    type: helm-registry
+    url: https://registry.example.com
+    username: octocat
+    password: ${{secrets.MY_REGISTRY_PASSWORD}}
+```
+
+{% endraw %}
+
+#### Notes
+
+{% data variables.product.prodname_dependabot %} works with any OCI-compliant registries that implement the Open Container Initiative (OCI) Distribution Specification. For more information, see [Helm Registry Login](https://helm.sh/docs/helm/helm_registry_login/) in the Helm docs.
+
+{% data variables.product.prodname_dependabot %} supports authentication to private registries via a central token service or HTTP Basic Auth. For more information, see [Token Authentication Specification](https://docs.docker.com/registry/spec/auth/token/) in the Docker documentation and [Basic access authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) on Wikipedia.
+
+When configuring Dependabot for Helm charts, it will also automatically update the Docker images referenced within those charts, ensuring that both the chart versions and their contained images stay up to date.
+
+#### Limitations and workarounds
+
+* {% data variables.product.prodname_dependabot %} only updates dependencies in `Chart.yaml` files.
+* Images in `values.yaml` files and `Chart.yaml` files are updated.
+* Helm dependency updates are first attempted via the Helm CLI, with fallback to searching `index.yaml`.
+* Images that have an array of versions in the YAML cannot be updated.
+* Image names may not always be detected in Helm files or YAML files.
+* For Helm v2 updates, use the [Docker ecosystem](#docker).
+
+{% endif %}
+
 ### Gradle
 
 {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to certain Gradle files. For more information, see "Gradle" in [AUTOTITLE](/code-security/dependabot/ecosystems-supported-by-dependabot/supported-ecosystems-and-repositories#gradle).
diff --git a/data/features/dependabot-helm-support.yml b/data/features/dependabot-helm-support.yml
new file mode 100644
index 000000000000..992b52f84aed
--- /dev/null
+++ b/data/features/dependabot-helm-support.yml
@@ -0,0 +1,6 @@
+# Reference: #17730
+# Helm Charts support for Dependabot
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '> 3.17'
diff --git a/data/reusables/dependabot/supported-package-managers.md b/data/reusables/dependabot/supported-package-managers.md
index d0748b1bc909..a2e76af1f680 100644
--- a/data/reusables/dependabot/supported-package-managers.md
+++ b/data/reusables/dependabot/supported-package-managers.md
@@ -18,6 +18,7 @@ Composer       | `composer`       | {% ifversion dependabot-updates-composerv1-c
 | {% ifversion dependabot-dotnet-sdk %} |
 .NET SDK       | `dotnet-sdk`         | >=.NET Core 3.1           | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} | Not applicable | Not applicable | Not applicable |
 | {% endif %} |
+[Helm Charts](#helm-charts)    | `helm`         | {% ifversion dependabot-helm-support %}v3{% else %}Not supported{% endif %} | {% ifversion dependabot-helm-support %}{% octicon "check" aria-label="Supported" %}{% else %}{% octicon "x" aria-label="Not supported" %}{% endif %} | {% octicon "x" aria-label="Not supported" %} | {% ifversion dependabot-helm-support %}{% octicon "check" aria-label="Supported" %}{% else %}{% octicon "x" aria-label="Not supported" %}{% endif %} | {% ifversion dependabot-helm-support %}{% octicon "check" aria-label="Supported" %}{% else %}{% octicon "x" aria-label="Not supported" %}{% endif %} | Not applicable |
 Hex            | `mix`            | v1               | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
 elm-package    | `elm`            | v0.19            | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
 git submodule  | `gitsubmodule`   | Not applicable | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | Not applicable |
@@ -112,6 +113,14 @@ For {% data variables.product.prodname_dependabot_security_updates %}, Gradle su
 > * When you upload Gradle dependencies to the dependency graph using the {% data variables.dependency-submission-api.name %}, all project dependencies are uploaded, even transitive dependencies that aren't explicitly mentioned in any dependency file. When an alert is detected in a transitive dependency, {% data variables.product.prodname_dependabot %} isn't able to find the vulnerable dependency in the repository, and therefore won't create a security update for that alert.
 > * {% data variables.product.prodname_dependabot_version_updates %} will, however, create pull requests when the parent dependency is explicitly declared as a direct dependency in the project's manifest file.
 
+#### Helm Charts
+
+{% data variables.product.prodname_dependabot %} supports using a username and password for registries. For more information, see [AUTOTITLE](/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot#helm-registry).
+
+{% data variables.product.prodname_dependabot %} works with any OCI-compliant registries that implement the Open Container Initiative (OCI) Distribution Specification.
+
+When configuring Dependabot for Helm charts, it will also automatically update the Docker images referenced within those charts, ensuring that both the chart versions and their contained images stay up to date.
+
 #### Maven
 
 {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files.

From c2d9ca8e75b48bb1f80e28c1e7a436e82a241e3e Mon Sep 17 00:00:00 2001
From: docs-bot <77750099+docs-bot@users.noreply.github.com>
Date: Fri, 11 Apr 2025 09:40:00 -0700
Subject: [PATCH 2/4] Sync secret scanning data (#55263)

Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
---
 src/secret-scanning/data/public-docs.yml | 2 +-
 src/secret-scanning/lib/config.json      | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/secret-scanning/data/public-docs.yml b/src/secret-scanning/data/public-docs.yml
index 6c7ce0bf738f..0746f8f70691 100644
--- a/src/secret-scanning/data/public-docs.yml
+++ b/src/secret-scanning/data/public-docs.yml
@@ -1689,7 +1689,7 @@
     ghes: '*'
   isPublic: false
   isPrivateWithGhas: true
-  hasPushProtection: false
+  hasPushProtection: true
   hasValidityCheck: '{% ifversion fpt or ghes %}false{% else %}true{% endif %}'
   isduplicate: false
 - provider: Google
diff --git a/src/secret-scanning/lib/config.json b/src/secret-scanning/lib/config.json
index 3691711cc336..416abec6a7c8 100644
--- a/src/secret-scanning/lib/config.json
+++ b/src/secret-scanning/lib/config.json
@@ -1,5 +1,5 @@
 {
-  "sha": "e5322c3dee0ad441a787d1bc0051420cf544bc24",
-  "blob-sha": "1ad7e3fecbf7e3fc6c67fbb61bdf8fe8c2891adb",
+  "sha": "7d6e6d0c21cf0c446584d4d7e3ef1766820a77a6",
+  "blob-sha": "db4351256cd9d9235a1958bea56834856b94cc7c",
   "targetFilename": "code-security/secret-scanning/introduction/supported-secret-scanning-patterns"
 }
\ No newline at end of file

From 53d1b0b4a6907815145c65139a219d1ce0e2dc2d Mon Sep 17 00:00:00 2001
From: Sunbrye Ly <56200261+sunbrye@users.noreply.github.com>
Date: Fri, 11 Apr 2025 09:51:13 -0700
Subject: [PATCH 3/4] Copilot Chat users can use the Gemini 2.5 Pro model
 (Public Preview) (#55242)

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Paul Loeb <90000203+thispaul@users.noreply.github.com>
Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com>
---
 ...ot-policies-as-an-individual-subscriber.md |  2 +-
 ...features-for-copilot-in-your-enterprise.md |  2 +-
 ...licies-for-copilot-in-your-organization.md |  2 +-
 .../about-premium-requests.md                 | 21 ++++----
 .../changing-the-ai-model-for-copilot-chat.md |  5 +-
 ...oosing-the-right-ai-model-for-your-task.md | 44 +++++++++++++--
 .../using-github-copilot/ai-models/index.md   |  2 +-
 .../using-gemini-flash-in-github-copilot.md   | 49 -----------------
 .../using-gemini-in-github-copilot.md         | 53 +++++++++++++++++++
 .../copilot/differences-cfi-cfb-table.md      | 21 ++++----
 data/reusables/copilot/gemini-model-info.md   |  2 +-
 .../copilot/model-use-cases/gemini-25-pro.md  |  3 ++
 data/variables/copilot.yml                    |  2 +
 13 files changed, 129 insertions(+), 79 deletions(-)
 delete mode 100644 content/copilot/using-github-copilot/ai-models/using-gemini-flash-in-github-copilot.md
 create mode 100644 content/copilot/using-github-copilot/ai-models/using-gemini-in-github-copilot.md
 create mode 100644 data/reusables/copilot/model-use-cases/gemini-25-pro.md

diff --git a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/managing-copilot-policies-as-an-individual-subscriber.md b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/managing-copilot-policies-as-an-individual-subscriber.md
index 81876fa08948..f92a75b10bca 100644
--- a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/managing-copilot-policies-as-an-individual-subscriber.md
+++ b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/managing-copilot-policies-as-an-individual-subscriber.md
@@ -54,7 +54,7 @@ You can choose whether your prompts and {% data variables.product.prodname_copil
 You can choose whether to allow the following AI models to be used as an alternative to {% data variables.product.prodname_copilot_short %}'s default model.
 
 * {% data variables.copilot.copilot_claude_sonnet %} - see [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-claude-sonnet-in-github-copilot)
-* {% data variables.copilot.copilot_gemini_flash %} - see [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-gemini-flash-in-github-copilot)
+* {% data variables.copilot.copilot_gemini %} - see [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-gemini-in-github-copilot)
 
 {% data reusables.user-settings.copilot-settings %}
 1. To the right of the model name, select the dropdown menu, then click **Enabled** or **Disabled**.
diff --git a/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise.md b/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise.md
index 2cf4b6b2972f..7d15b02c8617 100644
--- a/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise.md
+++ b/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise.md
@@ -93,7 +93,7 @@ Some features of {% data variables.product.prodname_copilot_short %} are availab
 By default, {% data variables.product.prodname_copilot_chat_short %} uses a base model. If you grant access to the alternative models, members of your enterprise can choose to use these models rather than the base model. The available alternative models are:
 
 * **{% data variables.copilot.copilot_claude_sonnet %}**. See [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-claude-sonnet-in-github-copilot).
-* **{% data variables.copilot.copilot_gemini_flash %}**. See [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-gemini-flash-in-github-copilot).
+* **{% data variables.copilot.copilot_gemini %}**. See [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-gemini-in-github-copilot).
 * **OpenAI's models:**
   * **o1**: This model is focused on advanced reasoning and solving complex problems, in particular in math and science. It responds more slowly than the GPT-4o model. Each member of your enterprise can make 10 requests to this model per day.
   * **o3-mini**: This is the next generation of reasoning models, following from o1 and o1-mini. The o3-mini model outperforms o1 on coding benchmarks with response times that are comparable to o1-mini, providing improved quality at nearly the same latency. It is best suited for code generation and small context operations. Each member of your enterprise can make 50 requests to this model every 12 hours. {% ifversion copilot-enterprise %}
diff --git a/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization.md b/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization.md
index f1fb5444882e..7448624807a5 100644
--- a/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization.md
+++ b/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization.md
@@ -37,7 +37,7 @@ Organization owners can set policies to govern how {% data variables.product.pro
 * Suggestions matching public code
 * Access to alternative models for {% data variables.product.prodname_copilot_short %}
   * Anthropic {% data variables.copilot.copilot_claude_sonnet %} in {% data variables.product.prodname_copilot_short %}
-  * Google {% data variables.copilot.copilot_gemini_flash %} in {% data variables.product.prodname_copilot_short %}
+  * Google {% data variables.copilot.copilot_gemini %} in {% data variables.product.prodname_copilot_short %}
   * OpenAI o1 and o3 models in {% data variables.product.prodname_copilot_short %}
 
 The policy settings selected by an organization owner determine the behavior of {% data variables.product.prodname_copilot %} for all organization members that have been granted access to {% data variables.product.prodname_copilot_short %} through the organization.
diff --git a/content/copilot/managing-copilot/monitoring-usage-and-entitlements/about-premium-requests.md b/content/copilot/managing-copilot/monitoring-usage-and-entitlements/about-premium-requests.md
index 20d2c0cb541a..d9aefa207e38 100644
--- a/content/copilot/managing-copilot/monitoring-usage-and-entitlements/about-premium-requests.md
+++ b/content/copilot/managing-copilot/monitoring-usage-and-entitlements/about-premium-requests.md
@@ -39,16 +39,17 @@ The following {% data variables.product.prodname_copilot_short %} features can u
 
 Each model has a premium request multiplier, based on its complexity and resource usage. Your premium request allowance is deducted according to this multiplier.
 
-| Model               | Premium requests |
-|--------------------------------------|------------|
-| Base model (GPT-4o)[^1]     | 0 (paid users), 1 ({% data variables.product.prodname_copilot_free_short %}) |
-| {% data variables.copilot.copilot_claude_sonnet_35 %}          | 1         |
-| {% data variables.copilot.copilot_claude_sonnet_37 %}          | 1         |
-| {% data variables.copilot.copilot_claude_sonnet_37 %} Thinking | 1.25      |
-| {% data variables.copilot.copilot_gemini_flash %}              | 0.25      |
-| GPT-4.5                       | 50        |
-| o1                            | 10         |
-| o3-mini                       | 0.33      |
+| Model                                                          | Premium requests                                                             |
+|----------------------------------------------------------------|------------------------------------------------------------------------------|
+| Base model (GPT-4o)[^1]                                        | 0 (paid users), 1 ({% data variables.product.prodname_copilot_free_short %}) |
+| {% data variables.copilot.copilot_claude_sonnet_35 %}          | 1                                                                            |
+| {% data variables.copilot.copilot_claude_sonnet_37 %}          | 1                                                                            |
+| {% data variables.copilot.copilot_claude_sonnet_37 %} Thinking | 1.25                                                                         |
+| {% data variables.copilot.copilot_gemini_flash %}              | 0.25                                                                         |
+| {% data variables.copilot.copilot_gemini_25_pro %}             | 1                                                                            |
+| GPT-4.5                                                        | 50                                                                           |
+| o1                                                             | 10                                                                           |
+| o3-mini                                                        | 0.33                                                                         |
 
 [^1]: Response times may vary during periods of high usage.
 
diff --git a/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-chat.md b/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-chat.md
index 2637a8839722..24dae7b4cad9 100644
--- a/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-chat.md
+++ b/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-chat.md
@@ -32,6 +32,7 @@ The following models are currently available in the immersive mode of {% data va
 * {% data variables.copilot.copilot_claude_sonnet_35 %}
 * {% data variables.copilot.copilot_claude_sonnet_37 %}
 * {% data variables.copilot.copilot_gemini_flash %}
+* {% data variables.copilot.copilot_gemini_25_pro %}
 * {% data variables.copilot.copilot_gpt_o1 %}
 * {% data variables.copilot.copilot_gpt_o3_mini %}
 
@@ -39,7 +40,7 @@ For more information about these models, see [AUTOTITLE](/copilot/using-github-c
 
 ### Limitations of AI models for {% data variables.product.prodname_copilot_chat_short %}
 
-* If you want to use the skills listed in the table above{% ifversion ghec %}, or knowledge bases{% endif %}, on the {% data variables.product.github %} website, only the GPT-4o, {% data variables.copilot.copilot_claude_sonnet %}, and {% data variables.copilot.copilot_gemini_flash %} models are supported.
+* If you want to use the skills listed in the table above{% ifversion ghec %}, or knowledge bases{% endif %}, on the {% data variables.product.github %} website, only the GPT-4o, {% data variables.copilot.copilot_claude_sonnet %}, and {% data variables.copilot.copilot_gemini %} models are supported.
 * Experimental pre-release versions of the models may not interact with all filters correctly, including the duplication detection filter.
 
 ## Changing your AI model
@@ -229,5 +230,5 @@ To use multi-model {% data variables.product.prodname_copilot_chat_short %}, you
 
 * [AUTOTITLE](/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-code-completion)
 * [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-claude-sonnet-in-github-copilot)
-* [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-gemini-flash-in-github-copilot)
+* [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-gemini-in-github-copilot)
 * [AUTOTITLE](/copilot/using-github-copilot/ai-models/choosing-the-right-ai-model-for-your-task)
diff --git a/content/copilot/using-github-copilot/ai-models/choosing-the-right-ai-model-for-your-task.md b/content/copilot/using-github-copilot/ai-models/choosing-the-right-ai-model-for-your-task.md
index 6a6a8ec56492..8f4a7c4c6c3e 100644
--- a/content/copilot/using-github-copilot/ai-models/choosing-the-right-ai-model-for-your-task.md
+++ b/content/copilot/using-github-copilot/ai-models/choosing-the-right-ai-model-for-your-task.md
@@ -29,7 +29,7 @@ You can click a model name in the list below to jump to a detailed overview of i
 * [{% data variables.copilot.copilot_claude_sonnet_35 %}](#claude-35-sonnet)
 * [{% data variables.copilot.copilot_claude_sonnet_37 %}](#claude-37-sonnet)
 * [{% data variables.copilot.copilot_gemini_flash %}](#gemini-20-flash)
-
+* [{% data variables.copilot.copilot_gemini_25_pro %}](#gemini-25-pro)
 > [!NOTE] Different models have different premium request multipliers, which can affect how much of your monthly usage allowance is consumed. For details, see [AUTOTITLE](/copilot/managing-copilot/monitoring-usage-and-entitlements/about-premium-requests).
 
 ## GPT-4o
@@ -278,8 +278,8 @@ The following table summarizes when an alternative model may be a better choice:
 
 {% data variables.copilot.copilot_gemini_flash %} is Google’s high-speed, multimodal model optimized for real-time, interactive applications that benefit from visual input and agentic reasoning. In {% data variables.product.prodname_copilot_chat_short %}, {% data variables.copilot.copilot_gemini_flash %} enables fast responses and cross-modal understanding.
 
-For more information about {% data variables.copilot.copilot_gemini_flash %}, see [Google's documentation](https://cloud.google.com/vertex-ai/generative-ai/docs/gemini-v2).
-For more information on using Gemini in {% data variables.product.prodname_copilot_short %}, see [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-gemini-flash-in-github-copilot).
+For more information about {% data variables.copilot.copilot_gemini_flash %}, see [Google's documentation](https://cloud.google.com/vertex-ai/generative-ai/docs/models/gemini/2-0-flash).
+For more information on using {% data variables.copilot.copilot_gemini %} in {% data variables.product.prodname_copilot_short %}, see [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-gemini-in-github-copilot).
 
 ### Use cases
 
@@ -314,6 +314,44 @@ The following table summarizes when an alternative model may be a better choice:
 
 {% endrowheaders %}
 
+## {% data variables.copilot.copilot_gemini_25_pro %}
+
+{% data variables.copilot.copilot_gemini_25_pro %} is Google's latest AI model, designed to handle complex tasks with advanced reasoning and coding capabilities. It also works well for heavy research workflows that require long-context understanding and analysis.
+
+For more information about {% data variables.copilot.copilot_gemini_25_pro %}, see [Google's documentation](https://cloud.google.com/vertex-ai/generative-ai/docs/models/gemini/2-5-pro).
+For more information on using {% data variables.copilot.copilot_gemini %} in {% data variables.product.prodname_copilot_short %}, see [AUTOTITLE](/copilot/using-github-copilot/ai-models/using-gemini-in-github-copilot).
+
+### Use cases
+
+{% data reusables.copilot.model-use-cases.gemini-25-pro %}
+
+### Strengths
+
+The following table summarizes the strengths of {% data variables.copilot.copilot_gemini_25_pro %}:
+
+{% rowheaders %}
+
+| Task                      | Description                                                       | Why {% data variables.copilot.copilot_gemini_flash %} is a good fit |
+|---------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------|
+| Complex code generation   | Write full functions, classes, or multi-file logic.               | Provides better structure, consistency, and fewer logic errors.     |
+| Debugging complex systems | Isolate and fix performance bottlenecks or multi-file issues.     | Provides step-by-step analysis and high reasoning accuracy.         |
+| Scientific research       | Analyze data and generate insights across scientific disciplines. | Supports complex analysis with heavy researching capabilities.      |
+| Long-context processing   | Analyze extensive documents, datasets, or codebases.              | 	Handles long-context inputs effectively.                           |
+
+{% endrowheaders %}
+
+### Alternative options
+
+The following table summarizes when an alternative model may be a better choice:
+
+{% rowheaders %}
+
+| Task                      | Description                                        | Why another model may be better                                                                            |
+|---------------------------|----------------------------------------------------|------------------------------------------------------------------------------------------------------------|
+| Cost-sensitive scenarios  | Tasks where performance-to-cost ratio matters.     | o3-mini or {% data variables.copilot.copilot_gemini_flash %} are more cost-effective for basic use cases.  |
+
+{% endrowheaders %}
+
 ## Further reading
 
 * [AUTOTITLE](/copilot/using-github-copilot/ai-models/examples-for-ai-model-comparison)
diff --git a/content/copilot/using-github-copilot/ai-models/index.md b/content/copilot/using-github-copilot/ai-models/index.md
index e749019abbc0..d6171c5e7676 100644
--- a/content/copilot/using-github-copilot/ai-models/index.md
+++ b/content/copilot/using-github-copilot/ai-models/index.md
@@ -10,7 +10,7 @@ children:
   - /changing-the-ai-model-for-copilot-chat
   - /changing-the-ai-model-for-copilot-code-completion
   - /using-claude-sonnet-in-github-copilot
-  - /using-gemini-flash-in-github-copilot
+  - /using-gemini-in-github-copilot
   - /choosing-the-right-ai-model-for-your-task
   - /comparing-ai-models-using-different-tasks
 ---
diff --git a/content/copilot/using-github-copilot/ai-models/using-gemini-flash-in-github-copilot.md b/content/copilot/using-github-copilot/ai-models/using-gemini-flash-in-github-copilot.md
deleted file mode 100644
index 9bdf9237215f..000000000000
--- a/content/copilot/using-github-copilot/ai-models/using-gemini-flash-in-github-copilot.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Using Gemini 2.0 Flash in Copilot Chat
-allowTitleToDifferFromFilename: true
-shortTitle: 'Use {% data variables.copilot.copilot_gemini_flash %}'
-intro: 'Learn how to enable {% data variables.copilot.copilot_gemini_flash %} in {% data variables.product.prodname_copilot_chat %}, for {% ifversion fpt %}yourself or{% endif %} your organization{% ifversion ghec %} or enterprise{% endif %}.'
-versions:
-  feature: copilot
-topics:
-  - Copilot
----
-
-## About {% data variables.copilot.copilot_gemini_flash %} in {% data variables.product.prodname_copilot %}
-
-{% data variables.copilot.copilot_gemini_flash %} is a large language model (LLM) that you can use as an alternative to the default model used by {% data variables.product.prodname_copilot_chat_short %}. {% data variables.copilot.copilot_gemini_flash %} is a responsive LLM that can empower you to build apps faster and more easily, so you can focus on great experiences for your users. {% data reusables.copilot.gemini-model-info %}
-
-{% data variables.copilot.copilot_gemini_flash %} is currently available in:
-
-* {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_vscode %}
-* Immersive mode in {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.github %}
-
-{% data variables.product.prodname_copilot %} uses {% data variables.copilot.copilot_gemini_flash %} hosted on Google Cloud Platform (GCP). When using {% data variables.copilot.copilot_gemini_flash %}, prompts and metadata are sent to GCP, which makes the [following data commitment](https://cloud.google.com/gemini/docs/discover/data-governance): _Gemini doesn't use your prompts, or its responses, as data to train its models._
-
-When using {% data variables.copilot.copilot_gemini_flash %}, input prompts and output completions continue to run through {% data variables.product.prodname_copilot %}'s content filters for public code matching, when applied, along with those for harmful, offensive, or off-topic content.
-
-## Configuring access
-
-You must enable access to {% data variables.copilot.copilot_gemini_flash %} before you can use the model.
-
-{% ifversion fpt %}
-
-### Setup for individual use
-
-If you have a {% data variables.product.prodname_copilot_free_short %} or {% data variables.product.prodname_copilot_pro_short %} subscription, you can enable {% data variables.copilot.copilot_gemini_flash %} in two ways:
-
-* The first time you choose to use {% data variables.copilot.copilot_gemini_flash %} with {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_vscode %}, or in the immersive view of {% data variables.product.prodname_copilot_chat_short %}, you will be prompted to allow access to the model.
-
-  Clicking **Allow** enables you to use {% data variables.copilot.copilot_gemini_flash %} and updates the policy in your personal settings on {% data variables.product.github %}.
-
-* You can enable the model directly in your personal settings on the {% data variables.product.github %} website. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-copilot-policies-as-an-individual-subscriber#enabling-or-disabling-alternative-ai-models).
-
-{% endif %}
-
-### Setup for organization {% ifversion ghec %}and enterprise{% endif %} use
-
-As an {% ifversion ghec %}enterprise or{% endif %} organization owner, you can enable or disable {% data variables.copilot.copilot_gemini_flash %} for everyone who has been assigned a {% ifversion ghec %}{% data variables.product.prodname_copilot_enterprise_short %} or {% endif %}{% data variables.product.prodname_copilot_business_short %} seat through your {% ifversion ghec %}enterprise or {% endif %}organization. See [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/setting-policies-for-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization){% ifversion ghec %} and [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise#copilot-access-to-alternative-ai-models){% endif %}.
-
-## Using {% data variables.copilot.copilot_gemini_flash %}
-
-For details of how to change the model that {% data variables.product.prodname_copilot_chat_short %} uses, see [AUTOTITLE](/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-chat).
diff --git a/content/copilot/using-github-copilot/ai-models/using-gemini-in-github-copilot.md b/content/copilot/using-github-copilot/ai-models/using-gemini-in-github-copilot.md
new file mode 100644
index 000000000000..7fd0b8b29d3f
--- /dev/null
+++ b/content/copilot/using-github-copilot/ai-models/using-gemini-in-github-copilot.md
@@ -0,0 +1,53 @@
+---
+title: Using Gemini in Copilot Chat
+allowTitleToDifferFromFilename: true
+shortTitle: 'Use {% data variables.copilot.copilot_gemini %}'
+intro: 'Learn how to enable {% data variables.copilot.copilot_gemini %} in {% data variables.product.prodname_copilot_chat %}, for {% ifversion fpt %}yourself or{% endif %} your organization{% ifversion ghec %} or enterprise{% endif %}.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+redirect_from:
+  - /copilot/using-github-copilot/ai-models/using-gemini-flash-in-github-copilot
+---
+
+## About {% data variables.copilot.copilot_gemini %} in {% data variables.product.prodname_copilot %}
+
+{% data variables.copilot.copilot_gemini %} models are large language models (LLMs) that you can use as an alternative to the default model used by {% data variables.product.prodname_copilot_chat_short %}. {% data variables.copilot.copilot_gemini %} models are responsive LLMs that can empower you to build apps faster and more easily, so you can focus on great experiences for your users. {% data reusables.copilot.gemini-model-info %}
+
+{% data variables.copilot.copilot_gemini %} is currently available in:
+
+* {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_vscode %}
+* Immersive mode in {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.github %}
+
+{% data variables.product.prodname_copilot %} uses {% data variables.copilot.copilot_gemini_flash %} and {% data variables.copilot.copilot_gemini_25_pro %} hosted on Google Cloud Platform (GCP). When using {% data variables.copilot.copilot_gemini %} models, prompts and metadata are sent to GCP, which makes the [following data commitment](https://cloud.google.com/gemini/docs/discover/data-governance): _{% data variables.copilot.copilot_gemini %} doesn't use your prompts, or its responses, as data to train its models._
+
+When using {% data variables.copilot.copilot_gemini %} models, input prompts and output completions continue to run through {% data variables.product.prodname_copilot %}'s content filters for public code matching, when applied, along with those for harmful, offensive, or off-topic content.
+
+## Configuring access
+
+You must enable access to {% data variables.copilot.copilot_gemini_flash %} and {% data variables.copilot.copilot_gemini_25_pro %} before you can use the model.
+
+{% ifversion fpt %}
+
+### Setup for individual use
+
+> [!NOTE] {% data variables.copilot.copilot_gemini_25_pro %} is not currently available for {% data variables.product.prodname_copilot_free_short %}.
+
+If you have a {% data variables.product.prodname_copilot_free_short %}, {% data variables.product.prodname_copilot_pro_short %}, or {% data variables.product.prodname_copilot_pro_plus_short %} subscription, you can enable {% data variables.copilot.copilot_gemini %} in two ways:
+
+* The first time you choose to use {% data variables.copilot.copilot_gemini %} models with {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_vscode %}, or in the immersive view of {% data variables.product.prodname_copilot_chat_short %}, you will be prompted to allow access to the model.
+
+  Clicking **Allow** enables you to use {% data variables.copilot.copilot_gemini %} and updates the policy in your personal settings on {% data variables.product.github %}.
+
+* You can enable the model directly in your personal settings on the {% data variables.product.github %} website. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-copilot-policies-as-an-individual-subscriber#enabling-or-disabling-alternative-ai-models).
+
+{% endif %}
+
+### Setup for organization {% ifversion ghec %}and enterprise{% endif %} use
+
+As an {% ifversion ghec %}enterprise or{% endif %} organization owner, you can enable or disable both {% data variables.copilot.copilot_gemini_flash %} and {% data variables.copilot.copilot_gemini_25_pro %} for everyone who has been assigned a {% ifversion ghec %}{% data variables.product.prodname_copilot_enterprise_short %} or {% endif %}{% data variables.product.prodname_copilot_business_short %} seat through your {% ifversion ghec %}enterprise or {% endif %}organization. See [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/setting-policies-for-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization){% ifversion ghec %} and [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise#copilot-access-to-alternative-ai-models){% endif %}.
+
+## Using {% data variables.copilot.copilot_gemini %}
+
+For details of how to change the model that {% data variables.product.prodname_copilot_chat_short %} uses, see [AUTOTITLE](/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-chat).
diff --git a/data/reusables/copilot/differences-cfi-cfb-table.md b/data/reusables/copilot/differences-cfi-cfb-table.md
index 3c71e06ee6a3..24f5f897ac73 100644
--- a/data/reusables/copilot/differences-cfi-cfb-table.md
+++ b/data/reusables/copilot/differences-cfi-cfb-table.md
@@ -41,16 +41,17 @@
 
 {% rowheaders %}
 
-| Available models in chat | {% data variables.product.prodname_copilot_free_short %} | {% data variables.product.prodname_copilot_pro_short %} | {% data variables.product.prodname_copilot_pro_plus_short %} | {% data variables.product.prodname_copilot_business_short %} | {% data variables.product.prodname_copilot_enterprise_short %} |
-| --- | --- | --- | --- | --- | --- |
-| {% data variables.copilot.copilot_claude_sonnet_35 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_sonnet_37 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_sonnet_37 %} Thinking | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gemini_flash %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| GPT-4o | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| GPT-4.5 | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} |
-| o1 | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| o3-mini | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| Available models in chat                                       | {% data variables.product.prodname_copilot_free_short %} | {% data variables.product.prodname_copilot_pro_short %} | {% data variables.product.prodname_copilot_pro_plus_short %} | {% data variables.product.prodname_copilot_business_short %} | {% data variables.product.prodname_copilot_enterprise_short %} |
+|----------------------------------------------------------------|----------------------------------------------------------| --- | --- | --- | --- |
+| {% data variables.copilot.copilot_claude_sonnet_35 %}          | {% octicon "check" aria-label="Included" %}              | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_sonnet_37 %}          | {% octicon "x" aria-label="Not included" %}              | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_sonnet_37 %} Thinking | {% octicon "x" aria-label="Not included" %}              | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gemini_flash %}              | {% octicon "check" aria-label="Included" %}              | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gemini_25_pro %}             | {% octicon "x" aria-label="Not included" %}              | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| GPT-4o                                                         | {% octicon "check" aria-label="Included" %}              | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| GPT-4.5                                                        | {% octicon "x" aria-label="Not included" %}              | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} |
+| o1                                                             | {% octicon "x" aria-label="Not included" %}              | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| o3-mini                                                        | {% octicon "check" aria-label="Included" %}              | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
 
 {% endrowheaders %}
 
diff --git a/data/reusables/copilot/gemini-model-info.md b/data/reusables/copilot/gemini-model-info.md
index ab736a008f40..1c03f0fa0bc2 100644
--- a/data/reusables/copilot/gemini-model-info.md
+++ b/data/reusables/copilot/gemini-model-info.md
@@ -1 +1 @@
-For information about the capabilities of {% data variables.copilot.copilot_gemini_flash %}, see the [Google for developers blog](https://developers.googleblog.com/en/the-next-chapter-of-the-gemini-era-for-developers/) and the [Google Cloud documentation](https://cloud.google.com/vertex-ai/generative-ai/docs/learn/models#gemini-2.0-flash). For details of Google's data handling policy, see [Generative AI and data governance](https://cloud.google.com/vertex-ai/generative-ai/docs/data-governance#prediction) on the Google website.
+For information about the capabilities of {% data variables.copilot.copilot_gemini %}, see the [Google for developers blog](https://developers.googleblog.com/en/gemini-2-5-flash-pro-live-api-veo-2-gemini-api/) and the [Google Cloud documentation](https://cloud.google.com/vertex-ai/generative-ai/docs/models). For details of Google's data handling policy, see [Generative AI and data governance](https://cloud.google.com/vertex-ai/generative-ai/docs/data-governance#prediction) on the Google website.
diff --git a/data/reusables/copilot/model-use-cases/gemini-25-pro.md b/data/reusables/copilot/model-use-cases/gemini-25-pro.md
new file mode 100644
index 000000000000..e0745f3104b1
--- /dev/null
+++ b/data/reusables/copilot/model-use-cases/gemini-25-pro.md
@@ -0,0 +1,3 @@
+{% data variables.copilot.copilot_gemini_25_pro %} is well-suited for advanced coding tasks, such as developing complex algorithms or debugging intricate codebases.
+It can assist with scientific research by analyzing data and generating insights across a wide range of disciplines. Its long-context capabilities allow it to manage and understand extensive documents or datasets effectively.
+{% data variables.copilot.copilot_gemini_25_pro %} is a strong choice for developers needing a powerful model.
diff --git a/data/variables/copilot.yml b/data/variables/copilot.yml
index d37173dc07c9..89e246a888a8 100644
--- a/data/variables/copilot.yml
+++ b/data/variables/copilot.yml
@@ -41,7 +41,9 @@ copilot_claude_sonnet: 'Claude Sonnet'
 copilot_claude_sonnet_35: 'Claude 3.5 Sonnet'
 copilot_claude_sonnet_37: 'Claude 3.7 Sonnet'
 
+copilot_gemini: 'Gemini'
 copilot_gemini_flash: 'Gemini 2.0 Flash'
+copilot_gemini_25_pro: 'Gemini 2.5 Pro'
 
 copilot_gpt_4o: 'GPT-4o'
 copilot_gpt_45: 'GPT-4.5'

From f5bc3655eb48bb1f8871608e64e8058cd0c601a2 Mon Sep 17 00:00:00 2001
From: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com>
Date: Fri, 11 Apr 2025 10:58:48 -0600
Subject: [PATCH 4/4] [Release note update]: Invalid Known Issue in release
 notes (#55239)

Co-authored-by: Vanessa <vgrl@github.com>
---
 data/release-notes/enterprise-server/3-12/0.yml  |  6 ++++++
 data/release-notes/enterprise-server/3-12/10.yml |  8 ++++++--
 data/release-notes/enterprise-server/3-12/11.yml | 10 +++++++---
 data/release-notes/enterprise-server/3-12/12.yml |  8 ++++++--
 data/release-notes/enterprise-server/3-12/13.yml |  8 ++++++--
 data/release-notes/enterprise-server/3-12/14.yml |  9 +++++++--
 data/release-notes/enterprise-server/3-12/15.yml |  6 ++++--
 data/release-notes/enterprise-server/3-12/2.yml  |  7 +++++--
 data/release-notes/enterprise-server/3-12/3.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-12/4.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-12/5.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-12/7.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-12/8.yml  |  8 +++++---
 data/release-notes/enterprise-server/3-12/9.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-13/10.yml |  8 ++++++--
 data/release-notes/enterprise-server/3-13/11.yml |  7 +++++--
 data/release-notes/enterprise-server/3-13/4.yml  |  9 ++++++---
 data/release-notes/enterprise-server/3-13/5.yml  |  9 +++++++--
 data/release-notes/enterprise-server/3-13/6.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-13/7.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-13/8.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-13/9.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-14/0.yml  |  6 ++++--
 data/release-notes/enterprise-server/3-14/1.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-14/2.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-14/3.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-14/4.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-14/5.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-14/6.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-14/7.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-14/8.yml  |  6 ++++--
 data/release-notes/enterprise-server/3-15/0.yml  |  9 +++++++--
 data/release-notes/enterprise-server/3-15/1.yml  |  9 +++++++--
 data/release-notes/enterprise-server/3-15/2.yml  |  8 ++++++--
 data/release-notes/enterprise-server/3-15/3.yml  |  7 +++++--
 35 files changed, 205 insertions(+), 71 deletions(-)

diff --git a/data/release-notes/enterprise-server/3-12/0.yml b/data/release-notes/enterprise-server/3-12/0.yml
index f075f7afe759..1047300c3a95 100644
--- a/data/release-notes/enterprise-server/3-12/0.yml
+++ b/data/release-notes/enterprise-server/3-12/0.yml
@@ -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]
+        
diff --git a/data/release-notes/enterprise-server/3-12/10.yml b/data/release-notes/enterprise-server/3-12/10.yml
index b4eb5163c86d..99421280f7d5 100644
--- a/data/release-notes/enterprise-server/3-12/10.yml
+++ b/data/release-notes/enterprise-server/3-12/10.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-12/11.yml b/data/release-notes/enterprise-server/3-12/11.yml
index 618ba0c825a5..ba781dc483fb 100644
--- a/data/release-notes/enterprise-server/3-12/11.yml
+++ b/data/release-notes/enterprise-server/3-12/11.yml
@@ -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.
- 
\ No newline at end of file
+ 
+  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]
+      
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-12/12.yml b/data/release-notes/enterprise-server/3-12/12.yml
index 67cb2b41e07a..1508c31358cb 100644
--- a/data/release-notes/enterprise-server/3-12/12.yml
+++ b/data/release-notes/enterprise-server/3-12/12.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-12/13.yml b/data/release-notes/enterprise-server/3-12/13.yml
index 028f9855e693..5d832e4ed4cd 100644
--- a/data/release-notes/enterprise-server/3-12/13.yml
+++ b/data/release-notes/enterprise-server/3-12/13.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-12/14.yml b/data/release-notes/enterprise-server/3-12/14.yml
index 7fa5173d288a..80f9e2f90fad 100644
--- a/data/release-notes/enterprise-server/3-12/14.yml
+++ b/data/release-notes/enterprise-server/3-12/14.yml
@@ -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]
+      
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-12/15.yml b/data/release-notes/enterprise-server/3-12/15.yml
index 443151eb0f6c..a735848496ee 100644
--- a/data/release-notes/enterprise-server/3-12/15.yml
+++ b/data/release-notes/enterprise-server/3-12/15.yml
@@ -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]
diff --git a/data/release-notes/enterprise-server/3-12/2.yml b/data/release-notes/enterprise-server/3-12/2.yml
index c78fc1a200f1..8b9c8e3acb03 100644
--- a/data/release-notes/enterprise-server/3-12/2.yml
+++ b/data/release-notes/enterprise-server/3-12/2.yml
@@ -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]
diff --git a/data/release-notes/enterprise-server/3-12/3.yml b/data/release-notes/enterprise-server/3-12/3.yml
index b31eaa656aa9..f2e3dcbc55f9 100644
--- a/data/release-notes/enterprise-server/3-12/3.yml
+++ b/data/release-notes/enterprise-server/3-12/3.yml
@@ -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]
diff --git a/data/release-notes/enterprise-server/3-12/4.yml b/data/release-notes/enterprise-server/3-12/4.yml
index 22882cb92209..01376c7e0967 100644
--- a/data/release-notes/enterprise-server/3-12/4.yml
+++ b/data/release-notes/enterprise-server/3-12/4.yml
@@ -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]
diff --git a/data/release-notes/enterprise-server/3-12/5.yml b/data/release-notes/enterprise-server/3-12/5.yml
index 725ef64e1b3f..f91177e15ae3 100644
--- a/data/release-notes/enterprise-server/3-12/5.yml
+++ b/data/release-notes/enterprise-server/3-12/5.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-12/7.yml b/data/release-notes/enterprise-server/3-12/7.yml
index 94a997dd4c1c..b6d135dfb2cf 100644
--- a/data/release-notes/enterprise-server/3-12/7.yml
+++ b/data/release-notes/enterprise-server/3-12/7.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-12/8.yml b/data/release-notes/enterprise-server/3-12/8.yml
index 803959d91993..c88471e0a7b6 100644
--- a/data/release-notes/enterprise-server/3-12/8.yml
+++ b/data/release-notes/enterprise-server/3-12/8.yml
@@ -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]
\ No newline at end of file
+      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]
diff --git a/data/release-notes/enterprise-server/3-12/9.yml b/data/release-notes/enterprise-server/3-12/9.yml
index 2a3deaa3db75..55d13daa9441 100644
--- a/data/release-notes/enterprise-server/3-12/9.yml
+++ b/data/release-notes/enterprise-server/3-12/9.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-13/10.yml b/data/release-notes/enterprise-server/3-13/10.yml
index 615d201feec2..384e712a5e60 100644
--- a/data/release-notes/enterprise-server/3-13/10.yml
+++ b/data/release-notes/enterprise-server/3-13/10.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-13/11.yml b/data/release-notes/enterprise-server/3-13/11.yml
index 31f057ed037b..57fea96f740c 100644
--- a/data/release-notes/enterprise-server/3-13/11.yml
+++ b/data/release-notes/enterprise-server/3-13/11.yml
@@ -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]
+      
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-13/4.yml b/data/release-notes/enterprise-server/3-13/4.yml
index dde7ff83c1b0..050c802e160c 100644
--- a/data/release-notes/enterprise-server/3-13/4.yml
+++ b/data/release-notes/enterprise-server/3-13/4.yml
@@ -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]
diff --git a/data/release-notes/enterprise-server/3-13/5.yml b/data/release-notes/enterprise-server/3-13/5.yml
index b25582c558b3..c464bfbb4e9b 100644
--- a/data/release-notes/enterprise-server/3-13/5.yml
+++ b/data/release-notes/enterprise-server/3-13/5.yml
@@ -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]
+      
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-13/6.yml b/data/release-notes/enterprise-server/3-13/6.yml
index 4dd579d8524a..1236b7e31a9e 100644
--- a/data/release-notes/enterprise-server/3-13/6.yml
+++ b/data/release-notes/enterprise-server/3-13/6.yml
@@ -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]
diff --git a/data/release-notes/enterprise-server/3-13/7.yml b/data/release-notes/enterprise-server/3-13/7.yml
index 4eb629034e31..044db4af29fc 100644
--- a/data/release-notes/enterprise-server/3-13/7.yml
+++ b/data/release-notes/enterprise-server/3-13/7.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-13/8.yml b/data/release-notes/enterprise-server/3-13/8.yml
index 6fa29d866384..bde600869a43 100644
--- a/data/release-notes/enterprise-server/3-13/8.yml
+++ b/data/release-notes/enterprise-server/3-13/8.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-13/9.yml b/data/release-notes/enterprise-server/3-13/9.yml
index 9f0750be7b58..e09bd1308215 100644
--- a/data/release-notes/enterprise-server/3-13/9.yml
+++ b/data/release-notes/enterprise-server/3-13/9.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-14/0.yml b/data/release-notes/enterprise-server/3-14/0.yml
index 1a3e878e3a32..ea8ca5911db1 100644
--- a/data/release-notes/enterprise-server/3-14/0.yml
+++ b/data/release-notes/enterprise-server/3-14/0.yml
@@ -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]
diff --git a/data/release-notes/enterprise-server/3-14/1.yml b/data/release-notes/enterprise-server/3-14/1.yml
index 899f09a893ec..1e9f55d3411a 100644
--- a/data/release-notes/enterprise-server/3-14/1.yml
+++ b/data/release-notes/enterprise-server/3-14/1.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-14/2.yml b/data/release-notes/enterprise-server/3-14/2.yml
index 9a87c808aade..c5efb8699aab 100644
--- a/data/release-notes/enterprise-server/3-14/2.yml
+++ b/data/release-notes/enterprise-server/3-14/2.yml
@@ -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]
diff --git a/data/release-notes/enterprise-server/3-14/3.yml b/data/release-notes/enterprise-server/3-14/3.yml
index 7ae837035003..7123bd9a0976 100644
--- a/data/release-notes/enterprise-server/3-14/3.yml
+++ b/data/release-notes/enterprise-server/3-14/3.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-14/4.yml b/data/release-notes/enterprise-server/3-14/4.yml
index 03660b2338fc..3a1a7f30352f 100644
--- a/data/release-notes/enterprise-server/3-14/4.yml
+++ b/data/release-notes/enterprise-server/3-14/4.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-14/5.yml b/data/release-notes/enterprise-server/3-14/5.yml
index 805b3a6ea6e3..425d48d3a7c4 100644
--- a/data/release-notes/enterprise-server/3-14/5.yml
+++ b/data/release-notes/enterprise-server/3-14/5.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-14/6.yml b/data/release-notes/enterprise-server/3-14/6.yml
index 0213ad49f561..e5ca1dbcff0d 100644
--- a/data/release-notes/enterprise-server/3-14/6.yml
+++ b/data/release-notes/enterprise-server/3-14/6.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-14/7.yml b/data/release-notes/enterprise-server/3-14/7.yml
index 0ea38ba4dc0c..b4b1d7a2112b 100644
--- a/data/release-notes/enterprise-server/3-14/7.yml
+++ b/data/release-notes/enterprise-server/3-14/7.yml
@@ -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]
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-14/8.yml b/data/release-notes/enterprise-server/3-14/8.yml
index e2fac4a0d24a..57842e92319f 100644
--- a/data/release-notes/enterprise-server/3-14/8.yml
+++ b/data/release-notes/enterprise-server/3-14/8.yml
@@ -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]
diff --git a/data/release-notes/enterprise-server/3-15/0.yml b/data/release-notes/enterprise-server/3-15/0.yml
index 4b9f1e5b0605..b2aaa90ad921 100644
--- a/data/release-notes/enterprise-server/3-15/0.yml
+++ b/data/release-notes/enterprise-server/3-15/0.yml
@@ -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]
+      
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-15/1.yml b/data/release-notes/enterprise-server/3-15/1.yml
index 13c0d25bf66a..abfeaf13d3cf 100644
--- a/data/release-notes/enterprise-server/3-15/1.yml
+++ b/data/release-notes/enterprise-server/3-15/1.yml
@@ -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]
+      
\ No newline at end of file
diff --git a/data/release-notes/enterprise-server/3-15/2.yml b/data/release-notes/enterprise-server/3-15/2.yml
index 3ab49e6dd885..f95f2c328073 100644
--- a/data/release-notes/enterprise-server/3-15/2.yml
+++ b/data/release-notes/enterprise-server/3-15/2.yml
@@ -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]
diff --git a/data/release-notes/enterprise-server/3-15/3.yml b/data/release-notes/enterprise-server/3-15/3.yml
index 67b3b27491d1..efdbadc09c81 100644
--- a/data/release-notes/enterprise-server/3-15/3.yml
+++ b/data/release-notes/enterprise-server/3-15/3.yml
@@ -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]
+      
\ No newline at end of file