Cram Sheet258 words
Topic 3.1 — Package management — cram sheet
Topic 3.1 — Package management · cram sheet
Tooling
Azure Artifacts' headline capability is upstream sources — proxy a public registry and save what it serves. That gives availability (survives outages and unpublished versions), auditability, and supply-chain integrity in one feature.
Feeds and views
| Fact | Detail |
|---|---|
| Default views | @local, @prerelease, @release |
| Default view | @local |
| Views are | Read-only |
| Publish target | Base feed only → appears in @local |
@local contains | Published packages + everything saved from upstream |
| Project-scoped | Visible in the hosting project; can be public (public project) |
| Organization-scoped | Org-wide; cannot be converted to project-scoped |
| Private feed minimum | Feed Reader |
| To act as an upstream for others | Visibility = members of org, or of your Microsoft Entra ID |
You cannot publish into @release. Publish to the feed, then promote.
Versioning
| SemVer part | Meaning |
|---|---|
| MAJOR | Breaking change |
| MINOR | Backward-compatible feature |
| PATCH | Backward-compatible fix |
- Pre-release sorts before the release:
2.0.0-rc.1<2.0.0. - CalVer when time is the meaningful axis.
- Current + reproducible + reviewable = range plus a committed lock file.
Artifact versioning
name:setsBuild.BuildNumber;$(Rev:.r)resets when the rest of the name changes.Build.BuildId= globally unique integer.Build.BuildNumber= the formatted name.- Must embed the commit SHA — the only unambiguous link to source.