GitHub Packages fine-grained PAT support #210789
Unanswered
krukowskid
asked this question in
Packages
Replies: 1 comment
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
Body
GitHub’s documentation strongly recommends using fine-grained Personal Access Tokens over classic PATs, yet GitHub Packages still exclusively supports classic PATs.
Despite community demand across Roadmap #558 and Discussion #38467, package registries remain incompatible with modern token security. Consequently, organizations enforcing fine-grained PATs cannot adopt GitHub Packages, blocking migrations from other platforms like Azure DevOps.
Please prioritize fine-grained PAT support across all package ecosystems (Docker/GHCR, npm, NuGet, Maven) to bring Packages into parity with the rest of the platform.
All reactions