Publishing Packages
Documentation menu
Publishing is the moment a build becomes a promise. Separate continuous integration packages from production releases so consumers know what they are installing.
Continuous integration builds
A package from a branch is useful for testing, but it should not look like a production release. Use a pre release identifier and publish it to a feed that is clearly marked for testing.
Production releases
A production release comes from a tagged commit, has a stable version and includes the matching changelog entry. Publish it only after the full test matrix is green.
Feed permissions
Limit who can publish to the production feed. A pipeline identity should have the smallest permission that lets it do its job. Rotate credentials when a person leaves the project.