Support public GitHub Packages feeds without a PAT #2071
Conversation
|
@microsoft-github-policy-service agree |
There was a problem hiding this comment.
Pull request overview
This PR enables support for reading from public GitHub Packages NuGet feeds without requiring a Personal Access Token (PAT). Instead, it uses the GITHUB_TOKEN (which has read:packages permissions) as the default authentication token when targeting GitHub Packages feeds. This addresses issue #2070.
Key Changes
- Automatically uses GITHUB_TOKEN for GitHub Packages feeds when no explicit token is configured
- Maintains backward compatibility with existing token configurations via AuthTokenSecret
- Updates release notes to document the new capability
Reviewed changes
Copilot reviewed 13 out of 13 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| RELEASENOTES.md | Documents the new support for public GitHub Packages feeds without PAT requirement |
| Actions/RunPipeline/RunPipeline.ps1 | Adds logic to automatically use GITHUB_TOKEN for GitHub Packages feed URLs when no explicit token is configured |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@microsoft-github-policy-service agree [company="Freddy.DK ApS"] |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
@microsoft-github-policy-service agree company="Freddy.DK ApS" |
|
Looks good! Just missing the license check @freddydk |
|
@microsoft-github-policy-service agree |
1 similar comment
|
@microsoft-github-policy-service agree |
|
microsoft-github-policy-service agree |
|
What more do I need to do, I have accepted license/cla 3 times |
4 participants
❔What, Why & How
Add read:packages permissions to the GITHUB_TOKEN and use that as default token when targetting GitHub Packages NuGet feeds to avoid having to create a PAT for public NuGet feeds.
This run in this repo: https://github.com/freddydk/TestRepo/actions/runs/20332336229 - is in a different organization than the trusted nuget feed and using the new functionality, this can now resolve the packages without a PAT
Related to issue: #2070
✅ Checklist