|
I’d like to manage a private RubyGems on GitHub Packages. And I’d like to use a personal access token or GitHub Apps’s token(installation access token) to authenticate. I could use a personal access token to authenticate. But i couldn’t use GitHub Apps’s token(installation access token). I explain here how to try.
GitHub Docs explains to use GitHub Packages with a personal access token to authenticate. But I didn’t find about using GitHub Packages with GitHub Apps. Can i use GitHub Packages with GitHub Apps now? Thank you. |
Replies: 16 comments 15 replies
|
hamuyuuki:
GitHub Packages doesn’t currently support GitHub App tokens. The only exception is the default GitHub Actions token, which is a special kind of app token. For the moment, you will need to use a PAT for programmatic access. Regards, |
|
Thank you for answering. I understand 😃 |
|
It would be great if adding package support to apps was considered as an improvement. At the moment to get packages access to a ruby gem for example you need:
Allowing a GitHub app to create tokens for package access would mean you:
Thanks! |
|
Any updates to this? This (and GitHub Packages support for fine-grained PATs, which I assume is related) is sorely needed functionality. GitHub applications like Renovate are blocked from working seamlessly with GitHub Packages and today require the use of user-associated, classic personal access tokens to fetch package information from GitHub Packages. |
|
Is PATs still the only option to use GitHub Packages? |
|
Any updates on this? |
|
Any news? |
|
It's a bug or not? Why deny access to packages with app token ? |
|
Similar to folks above, I was very confused by this. I was swapping my CICD from using my own personal access token to use GitHub App tokens. PAT obviously isn't great for CICD because it requires sharing personal credentials. The messaging I kept getting back from a
This was very confusing and had be quadruple checking app permissions, installs, and package settings to try and figure out what was preventing access. Looking online wasn't very helpful either as the GitHub docs indicate how to set up GitHub Actions access for this flow, but none explicitly mentioned that you couldn't use a GitHub App token so outside of GH actions. This all felt pretty bad, and is probably going to result in me moving my images elsewhere. |
|
any update? |
|
Hello from 2026, still not supported :) |
|
Same here, still not supported and still needed. GITHUB_TOKEN is not an option here, because we need to provide CI access to another repository of our organization |
|
Funny how every 2 years or so, I always end up trying to use gh apps for packages but then get stunned when it doesn't work and then I end up remembering that it really isn't supported. It's been 6 years now since this discussion opened- now I'm just stunned that it hasn't been fixed yet. |
|
This would be extremely useful to have implemented, pity its sitting with so much interest for so long :( |
|
It would be great to have GH apps to use GH packages. I did all option try with GH app permission on the package, but it says denied |


GitHub Packages doesn’t currently support GitHub App tokens. The only exception is the default GitHub Actions token, which is a special kind of app token. For the moment, you will need to use a PAT for programmatic access.
Regards,
Jamie.