docs/content/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md

title, intro, versions, type, topics, redirect_from, shortTitle

title	intro	versions	type	topics	redirect_from	shortTitle
Using the latest version of the official bundled actions	You can update the actions that are bundled with your enterprise, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.	ghes *	how_to	Actions Enterprise GitHub Connect	/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions /admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions	Use the latest bundled actions

{% data reusables.actions.enterprise-github-hosted-runners %}

Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see AUTOTITLE.

These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the actions-sync tool to update these actions, or you can configure {% data variables.product.prodname_github_connect %} to allow access to the latest actions on {% data variables.product.prodname_dotcom_the_website %}. These options are described in the following sections.

Using actions-sync to update the bundled actions

To update the bundled actions, you can use the actions-sync tool to update the snapshot. For more information on using actions-sync, see AUTOTITLE.

Using {% data variables.product.prodname_github_connect %} to access the latest actions

You can use {% data variables.product.prodname_github_connect %} to allow {% data variables.product.prodname_ghe_server %} to use actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see AUTOTITLE.

Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the actions organization on your instance. For example, if your enterprise instance is using v1 of the actions/checkout action, and you need to use {% data reusables.actions.action-checkout %} which isn't available on your enterprise instance, perform the following steps to be able to use the latest checkout action from {% data variables.product.prodname_dotcom_the_website %}:

1. From an enterprise owner account on {% data variables.product.prodname_ghe_server %}, navigate to the repository you want to delete from the actions organization (in this example checkout).

2. By default, site administrators are not owners of the bundled actions organization. To get the access required to delete the checkout repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="Site admin" %} in the upper-right corner of any page in that repository.

3. Click {% octicon "shield-lock" aria-hidden="true" aria-label="shield-lock" %} Security to see an overview of the security for the repository.

   

4. Under "Privileged access", click Unlock.

5. Under Reason, type a reason for unlocking the repository, then click Unlock.

6. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the actions organization. At the top of the page, click the repository name, in this example checkout, to return to the summary page.

   

7. Under "Repository info", click View code to leave the site admin pages and display the checkout repository.

   

8. Delete the checkout repository within the actions organization. For information on how to delete a repository, see AUTOTITLE.

9. Configure your workflow's YAML to use {% data reusables.actions.action-checkout %}.

10. Each time your workflow runs, the runner will use the specified version of actions/checkout from {% data variables.product.prodname_dotcom_the_website %}.

    Note

    The first time the checkout action is used from {% data variables.product.prodname_dotcom_the_website %}, the actions/checkout namespace is automatically retired on {% data variables.location.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see AUTOTITLE.