Docs update per https://github.com/github/docs-content/issues/16849 (#54627)

Co-authored-by: june1963 <22231680+june1963@users.noreply.github.com>
Co-authored-by: Felicity Chapman <felicitymay@github.com>

content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/removing-workflow-artifacts.md

@@ -38,3 +38,5 @@ You can also define a custom retention period for individual artifacts using the
 ## Finding the expiration date of an artifact
 
 You can use the API to confirm the date that an artifact is scheduled to be deleted. For more information, see the `expires_at` value returned by the REST API. For more information, see [AUTOTITLE](/rest/actions/artifacts).
+
+{% data reusables.actions.artifacts.artifacts-from-deleted-workflow-runs %}

content/actions/writing-workflows/choosing-what-your-workflow-does/storing-and-sharing-data-from-a-workflow.md

@@ -270,6 +270,8 @@ jobs:
 
 The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see [AUTOTITLE](/actions/managing-workflow-runs/downloading-workflow-artifacts).
 
+{% data reusables.actions.artifacts.artifacts-from-deleted-workflow-runs %}
+
 {% ifversion fpt or ghec %}
 
 ## Further reading

content/packages/learn-github-packages/about-permissions-for-github-packages.md

@@ -51,6 +51,8 @@ The following {% data variables.product.prodname_registry %} registries **only**
 
 For {% ifversion ghes %}the {% data variables.product.prodname_container_registry %}{% else %}other registries{% endif %}, you can choose to allow packages to be scoped to a user or an organization, or linked to a repository. {% ifversion ghes %}For information about migration to the {% data variables.product.prodname_container_registry %}, see [AUTOTITLE](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry).{% endif %}
 
+{% data reusables.package_registry.maven-package-visibility %}
+
 ## Visibility and access permissions for packages
 
 {% data reusables.package_registry.visibility-and-access-permissions %}

content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md

@@ -193,6 +193,8 @@ For registries that support granular permissions, you can choose the visibility
     * To enable organization members to create private packages that are only visible to other organization members, click **Private**. You can further customize the visibility of private packages.
     * To enable organization members to create internal packages that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the packages will be visible to all enterprise members.
 
+   {% data reusables.package_registry.maven-package-visibility %}
+
 ## Configuring visibility of packages for an organization
 
 When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your package through the access settings. Once you make your package public, you cannot make your package private again.

data/reusables/actions/artifacts/artifacts-from-deleted-workflow-runs.md

@@ -0,0 +1,3 @@
+## Artifacts from deleted workflow runs
+
+When a workflow run is deleted all artifacts associated with the run are also deleted from storage. You can delete a workflow run using the GitHub Actions UI, the REST API, or using the GitHub CLI, see: [AUTOTITLE](/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/deleting-a-workflow-run), [Delete a workflow run](/rest/actions/workflow-runs?apiVersion=2022-11-28#delete-a-workflow-run), or [gh run delete](https://cli.github.com/manual/gh_run_delete).

data/reusables/package_registry/maven-package-visibility.md

@@ -0,0 +1,4 @@
+{%- ifversion ghec %}
+> [!NOTE]
+> Maven and Gradle are currently only supported for public and private repository visibilities. Internal repository visibility is not supported.
+{% endif %}