Azure Artifacts feed views: publish, promote and resolution order

Verdict: You publish only to the base feed, where packages land in @local; @release is reached by promotion, never direct publish. On resolve, directly published packages win first, then packages saved from upstream, then upstream sources in configured order.

Azure Artifacts supports publishing and restoring only from @local; every other view is reached by promotion

1. Publish a package to the base feed - it appears in @local
2. @local also holds packages saved from configured upstream sources
3. Promote a validated @local version to reach @release
4. Consumers connected to @release only ever see promoted, validated versions
5. On resolution, directly published packages are searched first
6. Then packages saved from an upstream source are searched
7. Then upstream sources are queried in their configured listing order

Rules

• Packages publish only to the base feed (@local); @release is reached by promotion, not by direct publishing to a non-default view.
• @local contains packages published directly to the feed plus packages saved from upstream sources.
• Resolution search order is: directly published, then saved-from-upstream, then upstream sources in their configured order.

Traps

• Upstream sources populate @local with saved external packages; they do not enable direct publishing to @release.
• A package available upstream but never installed and saved is not yet stored in @local.
• Public registries are not searched before the feed's own packages; directly published packages win resolution.