Quick Notes109 words
Choosing package management tools — quick notes
Package tooling — quick notes
| Signal | Points to |
|---|---|
| Upstream proxying + saved copies | Azure Artifacts |
| Previously saved version survives an upstream outage | Azure Artifacts upstream sources |
| GitHub-native hosting and Actions/API integration | GitHub Packages |
| GitHub Packages permission scope | Depends on registry: user/organisation or repository |
| Azure Artifacts feed roles | Feed Reader · Feed and Upstream Reader (Collaborator) · Feed Publisher (Contributor) · Feed Owner |
Key idea: an upstream package is saved when installed by a Collaborator-or-higher. The saved version is immutable and gives the feed a centralised inventory with outage resilience.