Skip to content

Create and publish a baseline

  • Plan: Business or higher.
  • Permission: Manage packages (packages:write).
  • Every package you want in the baseline is in your catalog, with an approved version.
  1. Go to Packages › Baselines and choose Create baseline.
  2. Enter a Name and a short name. The short name (lowercase letters, numbers and dashes) is used in commands and can’t be reused.
  3. Open the baseline. A draft revision is ready.
  1. Choose Add package and Choose a package from your catalog.
  2. Choose Which version:
    • Newest approved version at publish, or
    • Pin to one approved version, then Choose the version to pin.
  3. Mark a package optional if it may be skipped. A package that installs only per user must be optional.
  4. Use Move earlier and Move later to set the install order.
  5. Choose the architectures the baseline covers. x64 and arm64 are the default.
  6. Choose Save draft.

A baseline holds up to 50 packages, each once.

  1. Check the Publish report under the draft. It shows what publishing would resolve: versions, installers per architecture and dependencies pulled in.
  2. Fix anything that blocks publishing. The report says what to do, for example Add the dependency to your catalog.
  3. Choose Publish revision 1.

“Published revision 1. Its winget import file is ready.” The revision is fixed. To change it, edit the next draft and publish again.

Report message Fix
A dependency isn’t in your catalog Add the dependency to your catalog and approve a version.
No approved versions Approve a version of that package first.
No installer for these architectures Remove the architecture from the baseline, or pick another package.
A member installs only per user Mark it optional.

To retire a baseline, choose Archive baseline. Archived baselines can’t be edited, published or assigned.