Issue with Github App authorization to pull private packages from Github registry

[krizzu]

🏷️ Discussion Type

Bug

Body

I'm trying to use a GitHub App installation token to pull private packages from the GitHub npm registry, but getting 403.

Setup:

• Created a GitHub App with Packages: Read repository permission
• Installed the app in our org with explicit access to the repositories where the npm packages are published
• Using actions/create-github-app-token@v3 in a custom action to generate an installation token
• Passing that token via npmAuthToken in .yarnrc.yml to authenticate against npm.pkg.github.com

And this gets me 403 Forbidden when Yarn tries to fetch @/package.
Is this known limitation? My understanding is that Github app should be able to pull in those packages without issue. I tried this flow with PAT and it works just fine.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[dhe-cruzer69]

[krizzu]

as a workaround, for package installation, I use workflow token with permission packages: read. This requires one to go to each package's settings and explicitly add which repository's github actions' workflow can access it