jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-06 06:02:35 -05:00
Code Issues Projects Releases Wiki Activity

Remove use of packages-delete-with-github-token-api feature (#50332)

Browse Source
This commit is contained in:
Peter Bengtsson
2024-04-26 07:37:30 -04:00
committed by GitHub
parent 0114cbac27
commit dcd99989fb
5 changed files with 4 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md
View File

@@ -2,8 +2,6 @@ For registries that support granular permissions, if your {% data variables.prod
{% data reusables.package_registry.delete-with-github-token-using-api-beta %}
{% ifversion packages-delete-with-github-token-api %}
You can use a `GITHUB_TOKEN` in a {% data variables.product.prodname_actions %} workflow to delete or restore a package using the REST API, if the token has `admin` permission to the package. Repositories that publish packages using a workflow, and repositories that you have explicitly connected to packages, are automatically granted `admin` permission to packages in the repository.
{% endif %}
For more information about the `GITHUB_TOKEN`, see "[AUTOTITLE](/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow)." For more information about the best practices when using a registry in actions, see "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)."

4
data/reusables/package_registry/delete-with-github-token-using-api-beta.md
View File

@@ -1,9 +1,5 @@
{% ifversion packages-delete-with-github-token-api %}
{% note %}
**Note:** The ability for {% data variables.product.prodname_actions %} workflows to delete and restore packages using the REST API is currently in public beta and subject to change.
{% endnote %}
{% endif %}

6
data/reusables/package_registry/visibility-and-access-permissions.md
View File

@@ -14,14 +14,12 @@ When you publish a package, you automatically get admin permissions to the packa
For packages scoped to a personal account, you can give any person an access role. For packages scoped to an organization, you can give any person or team in the organization an access role.
{% ifversion packages-delete-with-github-token-api %}
If you are using a {% data variables.product.prodname_actions %} workflow to manage your packages, you can grant an access role to the repository the workflow is stored in {% data variables.package_registry.package-settings-actions-access-menu %}. For more information, see "[AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
{% endif %}
| Permission | Access description |
|------------|--------------------|
| Read | Can download package. <br> Can read package metadata. |
| Write | Can upload and download this package. <br> Can read and write package metadata. |{% ifversion packages-delete-with-github-token-api %}
| Admin | Can upload, download, delete, and manage this package. <br> Can read and write package metadata. <br> Can grant package permissions.{% endif %}
| Write | Can upload and download this package. <br> Can read and write package metadata. |
| Admin | Can upload, download, delete, and manage this package. <br> Can read and write package metadata. <br> Can grant package permissions.
{% data reusables.package_registry.delete-with-github-token-using-api-beta %}