Related changelog post: Packages: Container registry now supports GITHUB_TOKEN - GitHub Changelog

However, switching from PAT to the GITHUB_TOKEN and adding permissions (push works fine with new token), now my custom action to list and then delete containers from ghcr.io throws:

HttpError: Resource not accessible by integration

Hi, @kc1r74p, welcome to the community.
the API you linked to states
Returns all package versions for a package owned by the authenticated user.
To use this endpoint, you must authenticate using an access token with the packages:read scope. If package_type is not container, your token must also include the repo scope.

The GITHUB_TOKEN secret is a GitHub App installation access token for a repository, it is not an authenticated user token, perhaps this explains the error message you see.

Thanks @byrneh,
yes I also thought that is most likely intentionally limited.

However which other API exists to read and delete containers if not those ?
As the changelog mentions even delete, I was hoping that these APIs would be supported,
as the only other alternative which I know of is to use the UI.

Best regards
Patrick

However which other API exists to read and delete containers if not those ?
As the changelog mentions even delete, I was hoping that these APIs would be supported,
as the only other alternative which I know of is to use the UI.

Best regards
Patrick

Hi,
packages#get-all-package-versions-for-a-package-owned-by-a-user returns details for a user, rather than the authenticated user.
Additionally, you will need to have have set appropriate access permissions
configuring-access-control-and-visibility-for-container-images

Hi,
packages#get-all-package-versions-for-a-package-owned-by-a-user returns details for a user, rather than the authenticated user.
Additionally, you will need to have have set appropriate access permissions
configuring-access-control-and-visibility-for-container-images

I checked the user specific one as well, and it fails with the same message.
I also rechecked the permissions, and pushing containers works fine with the GITHUB_TOKEN.
So I am not seeing any other, more specific way to enable these APIs for the generic token.

Thanks none the less for checking!
I will wait and see if there will be further information, I could imagine as it is beta, that it will just take some more time.

Best regards,
Patrick

Hi @shayneburgess , is there any progress here? 1 year later? Deleting a package via API and GITHUB_TOKEN seems like a pretty basic feature?

@shayneburgess, any progress? I think deleting a pakcage via API and GITHUB_TOKEN is very usefull for me.