Merge pull request #37579 from github/repo-sync

Repo sync

Author: docs-bot

content/code-security/securing-your-organization/enabling-security-features-in-your-organization/giving-org-access-private-registries.md

@@ -17,8 +17,6 @@ When a repository uses code stored in a private registry, some security features
 
 ## {% data variables.product.prodname_code_scanning_caps %} default setup access to private registries
 
-{% data reusables.code-scanning.preview-org-private-registry %}
-
 {% data variables.product.prodname_code_scanning_caps %} default setup analyzes {% data variables.code-scanning.no_build_support %} code without building it. If you do not define access to the private registries your organization uses, then {% data variables.product.prodname_code_scanning %} will only gather necessary data from dependencies available in public registries. Most times, this is enough for surfacing most of the vulnerabilities. However, in some cases the lack of access can lead to false negative results, that is, {% data variables.product.prodname_code_scanning %} is unable to detect a vulnerability in the code because it does not have all the information it needs to analyze the code. For example, some of the data flow paths may not be detected because steps are defined in dependencies that are not accessible and {% data variables.product.prodname_code_scanning %} does not know how to interpret them.
 
 When you configure access to the private registries used in your organization, {% data variables.product.prodname_code_scanning %} has access to all the information it needs and is much less likely to miss a vulnerability.

content/rest/private-registries/organization-configurations.md

@@ -12,7 +12,5 @@ autogenerated: rest
 allowTitleToDifferFromFilename: true
 ---
 
-> [!NOTE]
-> The ability to use the REST API to manage private registries is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 <!-- Content after this section is automatically generated -->

data/features/org-private-registry.yml

@@ -4,3 +4,4 @@
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '>=3.18'