Co-authored-by: Hirsch Singhal <1666363+hpsin@users.noreply.github.com> Co-authored-by: Jovel Crisostomo <jovel@github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Vanessa <vgrl@github.com>
1.2 KiB
{% data reusables.package_registry.packages-classic-pat-only %}
You need an access token to publish, install, and delete private, internal, and public packages.
You can use a {% data variables.product.pat_v1 %} to authenticate to {% data variables.product.prodname_registry %} or the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. When you create a {% data variables.product.pat_v1 %}, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a {% data variables.product.pat_v1 %}, see "About permissions for GitHub Packages."
To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use:
GITHUB_TOKENto publish packages associated with the workflow repository.- a {% data variables.product.pat_v1 %} with at least
packages:readscope to install packages associated with other private repositories (whichGITHUB_TOKENcan't access).