Skip to content

Fix packages.microsoft.com publishing to have different packagename for previews - #1747

Merged
Mikey Lombardi (He/Him) (michaeltlombardi) merged 2 commits into
PowerShell:mainfrom
SteveL-MSFT:pmc-preview
Oct 9, 2026
Merged

Mikey Lombardi (He/Him) (michaeltlombardi) merged 2 commits into
PowerShell:mainfrom
SteveL-MSFT:pmc-preview

Conversation

@SteveL-MSFT

Copy link
Copy Markdown
Member

PR Summary

Previously, whether a stable or preview version being published to packages.microsoft.com, the package name was dsc so whenever we published a new preview, that would be the newer version over a stable even if the user didn't plan to install a preview.

Fix is to have a different package name for preview releases so that:

apt install dsc

and

apt install dsc-preview

are distinct packages (even if the exe name is the same)

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Preview artifacts and package metadata remain named dsc, causing publishing failure and preventing distinct installation.

1 open finding
What changed in this PR

Updates PMC publishing logic to distinguish preview and stable package names.

Changes:

  • Selects dsc-preview for prerelease versions.
  • Retains dsc for stable versions.
File Description
.pipelines/​EV2Specs/​ServiceGroupRoot/​Shell/​Run/​Run.ps1 Selects the package name and channel by release type.

🧠 Review effort: Balanced


💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread .pipelines/EV2Specs/ServiceGroupRoot/Shell/Run/Run.ps1
Merged via the queue into PowerShell:main with commit a751adc Oct 9, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants