Merge pull request #33672 from github/repo-sync

Repo sync

Author: docs-bot

content/actions/security-guides/using-artifact-attestations-and-reusable-workflows-to-achieve-slsa-v1-build-level-3.md

@@ -14,8 +14,6 @@ versions:
   ghec: '*'
 ---
 
-{% data reusables.actions.artifact-attestations-public-beta-note %}
-
 ## Introduction
 
 Artifact attestations are a great way to create unfalsifiable provenance and integrity guarantees for the software you build.

content/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds.md

@@ -7,8 +7,6 @@ versions:
 shortTitle: Artifact attestations
 ---
 
-{% data reusables.actions.artifact-attestations-public-beta-note %}
-
 ## About artifact attestations
 
 {% data reusables.actions.about-artifact-attestations %}

content/actions/using-workflows/storing-workflow-data-as-artifacts.md

@@ -124,8 +124,6 @@ jobs:
 
 ## Generating artifact attestations for builds
 
-{% data reusables.actions.artifact-attestations-public-beta-note %}
-
 {% data reusables.actions.about-artifact-attestations %}
 
 You can access attestations after a build run, underneath the list of the artifacts the build produced.

content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance.md

@@ -203,3 +203,10 @@ For more information about restoring from a failed upgrade, see "[AUTOTITLE](/ad
 
 If your appliance averages more than 70% CPU utilization, {% data variables.product.company_short %} strongly recommends scaling up your server resources before upgrading to 3.11 or above. The new hardware or instance type should have more vCPUs to accommodate the additional load from new features and improvements included with the latest releases.
 {% endif %}
+
+{% ifversion ghes > 3.12 and ghes < 3.15 %}
+
+## Elasticsearch Upgrade
+
+As part of upgrading GitHub Enterprise Server to version 3.13 or later, the Elasticsearch service will be upgraded. {% data variables.product.company_short %} strongly recommends following the guidance in "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/preparing-for-the-elasticsearch-upgrade)."
+{% endif %}

content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md

@@ -43,8 +43,6 @@ In addition to the security benefits, {% data variables.product.prodname_actions
 
 ## Generate artifact attestations for your builds
 
-{% data reusables.actions.artifact-attestations-public-beta-note %}
-
 {% data reusables.actions.about-artifact-attestations %}
 
 Artifact attestations include a signature over a built artifact, along with links to the source code and build instructions. If you sign your build with artifact attestations, you do not have to manage your own signing key material. {% data variables.product.prodname_dotcom %} handles this for you with the signing authority we operate.

data/reusables/actions/artifact-attestations-public-beta-note.md

@@ -3,5 +3,5 @@
     "apiOnlyEvents": "This event is not available in the web interface, only via the REST API, audit log streaming, or JSON/CSV exports.",
     "apiRequestEvent": "This event is only available via audit log streaming."
   },
-  "sha": "696298e01ede2e0c4b5b112aed8cccf548c35511"
+  "sha": "722817aced5cc835d69929a16d3424b50298ec6f"
 }